https://durable.rocks/docs/use-cases/Recent content in Use cases on DurableHugoen-UShttps://durable.rocks/docs/use-cases/nexus-demo/Mon, 01 Jan 0001 00:00:00 +0000https://durable.rocks/docs/use-cases/nexus-demo/<h1 id="four-applications-calling-each-other">Four applications calling each other<a class="anchor" href="#four-applications-calling-each-other">#</a></h1> <h2 id="the-problem">The problem<a class="anchor" href="#the-problem">#</a></h2> <p>An order crosses four systems owned by four different teams: the shop holds stock, the business side invoices, logistics plans and ships, the ERP follows. Each has its own repository, framework and release cadence. None of them wants to import another one&rsquo;s code.</p> <p>The usual way to stitch that together (one HTTP API per service, one client per caller, one retry per client, one timeout per retry) works until one of the four is down mid-transaction. Then someone has to decide whether to wait, whether to replay, and what happens to what was already taken.</p>