From the course: .NET Microservices for Azure Developers

Unlock the full course today

Join today to access over 24,800 courses taught by industry experts.

Communication between microservices

Communication between microservices - Azure Tutorial

From the course: .NET Microservices for Azure Developers

Start my 1-month free trial Buy for my team

Communication between microservices

“

- [Presenter] In a microservices architecture, you'll often need to communicate between services. This can be achieved in two primary ways: synchronously or asynchronously. With a synchronous approach, the target service exposes an API, which the initiating service knows in advance. This communication generally occurs through the HTTP protocol, though it's not limited to it. One of the major advantages of this method is its simplicity. However, it has some drawbacks. Services are different processes. Meaning service A may call service B across the network, leading to potential scaling challenges. If service B is slow or unresponsive, service A will be delayed waiting for it. To mitigate this, you should implement resilience features in your application such as automatic retries in case of communication failures. If these failures persist, a circuit breaker pattern can be employed to indicate that a particular operation or functionality is temporarily unavailable. Remember, everything…

Contents