There are multiple things to consider when creating reactive systems. Orchestration with reactive APIs is not easy and often error-prone. Introducing a message broker to handle and manage asynchronous communication is common practice in reactive systems and leads to message-driven architectures. In such architectures, it becomes harder to manage and monitor the state of your systems. Having transparency about the state is essential, especially considering more complex principles, for example, the Saga Pattern. This talk introduces ways how to manage the state in a reactive system. It outlines the concept of modern workflow engines and ways to integrate them into your Java environment with message brokers or use them in a standalone fashion.