![]() However, in projects where the tasks performed by microservices are connected in a logical sequence or there are numerous microservices, you should opt for orchestration. Therefore, choreography will be a good choice in the case of projects that have a limited number of microservices or where tasks are not executed by microservices in a fixed order. This approach, where a process is managed in a distributed way by many microservices, is called “choreography.” If you want to change the process, e.g., add a new microservice, you need to modify the existing ones. So, each microservice generates events informing the next one what happens next. If the first microservice does not know about the existence of the second one, at least it should know what event type it should publish. After completing a task, a microservice has to send a message on what is to be done next, e.g., send an event to the queue of another microservice. Here, there are two possible approaches.Įven using a queue, you can make microservices dependent upon one another. If the microservices in the app need to work independently from one another, the best option to choose is a queue. If you decide to apply the microservice approach in your IT project, you need to choose an appropriate communication method between the microservices. In this article, you will learn how we solved the problem of microservice orchestration and why MassTransit makes a really good choice in this case. Therefore, we decided to use it when building a custom document generation solution. Microservice architecture has already become a widespread approach to IT infrastructure planning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |