https://ricardozanini.github.io/tags/messaging/Recent content in Messaging on Ricardo ZaniniHugoenFri, 31 Jul 2026 10:40:34 -0400https://ricardozanini.github.io/2026/07/31/how-quarkus-flow-talks-to-the-world-the-messaging-architecture/Fri, 31 Jul 2026 00:00:00 +0000https://ricardozanini.github.io/2026/07/31/how-quarkus-flow-talks-to-the-world-the-messaging-architecture/<p>A workflow engine that can&rsquo;t talk to the outside world is just a fancy state machine running in isolation. The moment you need event-driven orchestration — pausing for a human approval, reacting to an external signal, emitting a domain event — you need a messaging bridge. And building one forces a decision: do you couple to Kafka? AMQP? Roll your own CloudEvent serialization and hope every connector plays nice?</p> <p>In <a href='https://ricardozanini.github.io/2026/05/15/what-are-workflows-and-why-do-i-need-them/' target="_blank">previous posts</a>, we explored why declarative workflows beat hand-rolled state machines and how Petri net semantics power parallel execution. This post goes one layer deeper: <strong>how Quarkus Flow actually moves events in and out of the engine</strong>, and why the answer is simpler than you might expect.</p>