Closed ephraa closed 2 years ago
github-actions[bot]
commented
2 years ago 👋 @ephraa Good afternoon and thank you for submitting your topic suggestion. Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.
hectorkambow
commented
2 years ago Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts. Please feel free to suggest an alternate topic to explore. 🚀
We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic it has to serve value to the larger developer community at large. Please feel free to suggest an alternate topic to explore. 🚀
Proposed title of article
Understanding orchestration patterns in microservices
Proposed article introduction
Microservices have continually gained popularity as an architectural style. A well-designed microservices offer a great alternative to monolithic architecture. However, as microservices grow in size the way they interact with each other changes and poses a real problem.
A direct call microservice pattern leads to tightly coupled services which in turn results in the distributed monolith. To avoid building a distributed monolith we implement event-driven microservices. The communication between event-driven microservices is asynchronous. If we remove tight coupling in between services, we can reap the benefits offered by the microservices architecture pattern.
Event-driven messaging is implemented in two different ways, the choreography, and orchestration pattern. The problem with the choreography pattern is that it is not suitable for complex business workflows and if there is a huge number of services. The proposed article expands more on the orchestrated event-driven pattern.
Key takeaways
At the end of the article the reader will be able to:
Article quality
The proposed article gives the practical example of modeling an orchestrated event-driven architecture with clear written steps.
References
N/A