Orchestration or choreography? Sagas or process manager? REST, RPC, or events? Are we just making this all up as we go along?
Microservices introduce major complexities the moment we move away from a single service and process to multiple ones. Immediately, the problem hits: services have to communicate. The architect mandates REST. But nothing works in production. Then come events. But nothing is ever completed. So now what?
Let’s look at the problem holistically: We want to uphold the fundamental autonomy of any microservice-based architecture while designing a communication strategy that enables services to achieve their purpose in the world.
That’s where patterns come in. In his talk from DDD Dallas, Jimmy looks at some basic communication patterns to see where we might run into problems and how advanced conversational patterns can help. He’ll walk you through some real-world scenarios to demonstrate how complex coordination and conversation patterns can get services communicating effectively while retaining our all-important autonomy and loose coupling.