You build your applications on microservices architecture. You like the fact that you can follow the single responsibility principle and build services that can be independently scaled and reasoned about. A typical business application requires coordination across multiple microservices.

This creates a dilemma, where do you put the coordination logic: Is this a new service, do services publish messages to Kafka (Yay!)?

In this session, we will learn about the pitfalls of invariably building a distributed monolith, challenges that comes with it and how we can leverage Apache Kafka with an orchestrator like Netflix Conductor to make a distributed stateful microservices based application that provides agility that you desire with operational visibility, control and more importantly correctness of the distributed system.