Nowadays, a single page on an Android app or a web page shows lots of different categories of data. If any system is backed by microservice architecture, then it is not possible to generate different categories of data produced by a single microservice. Different microservices help in producing such categorized data, which leads to lots of communication between different microservices.

While dealing with a monolithic application, the whole code base resides at the same place and in the same language. So, communication between different modules happens through the function call or method call. However, this cannot be the case with microservices. Each microservice is a different process that runs in a completely different context or may be on different hardware. There are different perspectives to look at the inter-microservice pattern.

From one perspective, the flow of control and communication between microservices can be categorized into the following categories:

• Orchestration
• Choreography