<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Petri Nets on Ricardo Zanini</title><link>https://ricardozanini.github.io/tags/petri-nets/</link><description>Recent content in Petri Nets on Ricardo Zanini</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 27 May 2026 20:49:27 -0400</lastBuildDate><atom:link href="https://ricardozanini.github.io/tags/petri-nets/index.xml" rel="self" type="application/rss+xml"/><item><title>The Mathematical Root: Petri Nets and Parallel Executions</title><link>https://ricardozanini.github.io/2026/05/27/the-mathematical-root-petri-nets-and-parallel-executions/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><guid>https://ricardozanini.github.io/2026/05/27/the-mathematical-root-petri-nets-and-parallel-executions/</guid><description>&lt;p&gt;In our previous discussion on the &lt;a href="https://ricardozanini.github.io/2026/05/15/what-are-workflows-and-why-do-i-need-them/"&gt;&amp;ldquo;polling trap,&amp;rdquo;&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description></item></channel></rss>