Mixing choreography and orchestration in a microservice architecture can provide several benefits. Choreography allows for flexibility and autonomy in the interactions between microservices, as each service can communicate directly with other services without needing a central authority. This can lead to more decentralized and resilient systems. On the other hand, orchestration can provide a centralized approach to controlling and coordinating the interactions between microservices, which can simplify the management and troubleshooting of the system. By combining both approaches, a microservice architecture can gain the benefits of both, flexibility and simplicity.

In this talk we are going to explore several patterns on how we can build a clean loosely-coupled architecture featuring a workflow engine, a message broker and our domain services. We are not only going to dive deep in theory but also going to talk through practical examples written in Java.

In the end you will be able to argument on when to use which style of architecture and know how to structure your code accordingly.