https://ricardozanini.github.io/tags/quarkus-flow/Recent content in Quarkus Flow on Ricardo ZaniniHugoenWed, 27 May 2026 20:49:27 -0400https://ricardozanini.github.io/2026/05/27/the-mathematical-root-petri-nets-and-parallel-executions/Wed, 27 May 2026 00:00:00 +0000https://ricardozanini.github.io/2026/05/27/the-mathematical-root-petri-nets-and-parallel-executions/<p>In our previous discussion on the <a href="https://ricardozanini.github.io/2026/05/15/what-are-workflows-and-why-do-i-need-them/">&ldquo;polling trap,&rdquo;</a> we established that managing long-running state is an infrastructure concern, not a business logic one. But when we move beyond simple pauses and step into the realm of concurrent execution, the architectural friction multiplies exponentially.</p> <p>Consider a standard e-commerce order process. When a user checks out, the system must perform two discrete remote operations: (a) reserve the items via the Inventory service, and (b) calculate the delivery routes via the Logistics service.</p>https://ricardozanini.github.io/2026/05/15/what-are-workflows-and-why-do-i-need-them/Fri, 15 May 2026 00:00:00 +0000https://ricardozanini.github.io/2026/05/15/what-are-workflows-and-why-do-i-need-them/<p>In distributed architectures, managing the state of a paused or long-running process is the fastest way to entangle your core business logic with infrastructure. Consider a seemingly straightforward process: an employee requests access to a secure cloud environment.</p> <p>The sequence is simple: (a) log the request, (b) wait for a manager to approve it, and then (c) provision the access.</p> <p>The inherent challenge is time. The manager might approve it in five seconds, or they might be on vacation for three days. You obviously aren&rsquo;t going to use <code>Thread.sleep()</code> and hold a server thread hostage waiting for a response.</p>