Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microservices Design Patterns in .NET

You're reading from   Microservices Design Patterns in .NET Making sense of microservices design and architecture using .NET Core

Arrow left icon
Product type Paperback
Published in Jan 2023
Publisher Packt
ISBN-13 9781804610305
Length 300 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Trevoir Williams Trevoir Williams
Author Profile Icon Trevoir Williams
Trevoir Williams
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Part 1: Understanding Microservices and Design Patterns
2. Chapter 1: Introduction to Microservices – the Big Picture FREE CHAPTER 3. Chapter 2: Working with the Aggregator Pattern 4. Chapter 3: Synchronous Communication between Microservices 5. Chapter 4: Asynchronous Communication between Microservices 6. Chapter 5: Working with the CQRS Pattern 7. Chapter 6: Applying Event Sourcing Patterns 8. Part 2: Database and Storage Design Patterns
9. Chapter 7: Handling Data for Each Microservice with the Database per Service Pattern 10. Chapter 8: Implement Transactions across Microservices Using the Saga Pattern 11. Part 3: Resiliency, Security, and Infrastructure Patterns
12. Chapter 9: Building Resilient Microservices 13. Chapter 10: Performing Health Checks on Your Services 14. Chapter 11: Implementing the API and BFF Gateway Patterns 15. Chapter 12: Securing Microservices with Bearer Tokens 16. Chapter 13: Microservice Container Hosting 17. Chapter 14: Implementing Centralized Logging for Microservices 18. Chapter 15: Wrapping It All Up 19. Index 20. Other Books You May Enjoy

Implementing synchronous communication

Synchronous communication means that we make a direct call from one service to another and wait for a response. Given all the fail-safes and retry policies that we could implement, we still evaluate the success of the call based on us receiving a response to our call.

In the context of our hospital management system, a simple query from the frontend will need to be done synchronously. If we need to see all the doctors in the system to present a list to the user, then we need to invoke a direct call to the doctors’ API microservice, which fetches the records from the database and returns the data with, more than likely, a 200 response that depicts success. Of course, this needs to happen as quickly and efficiently as possible, as we want to reduce the amount of time the user spends waiting on the results to be returned.

There are several methods that we can use to make an API call, and HTTP is the most popular. Support for HTTP calls...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image