Event-Driven Architectures

Abstract

In the previous chapter, we analyzed how the interface between our microservices plays a key role concerning tight coupling. The Multiplication microservice calls the Gamification microservice, becoming the orchestrator of the process. If there were other services that also needed to get the attempts, we would need to add extra calls from the Multiplication application, thus creating a distributed monolith with a central brain. We covered this problem in detail when we examined a hypothetical extension of our back end.