https://durable.rocks/posts/Recent content in Blog on DurableHugoen-UShttps://durable.rocks/posts/nexus-bounded-contexts/Mon, 07 Sep 2026 00:00:00 +0000https://durable.rocks/posts/nexus-bounded-contexts/<h1 id="the-nexus-stub-is-an-adapter-not-a-port">The Nexus stub is an adapter, not a port<a class="anchor" href="#the-nexus-stub-is-an-adapter-not-a-port">#</a></h1> <p>Most of us learned the rule and repeat it without re-deriving it: a bounded context does not call another bounded context synchronously. Herberto Graça states it in <a href="https://herbertograca.com/2017/11/16/explicit-architecture-01-ddd-hexagonal-onion-clean-cqrs-how-i-put-it-all-together/">Explicit Architecture</a>, where components stay decoupled to the point that &ldquo;a component has no direct knowledge of any other component&rdquo;, and where they must talk he reaches for events and eventual consistency.</p> <p>The reason is availability. B goes down, you fail. B slows, you slow. B&rsquo;s deploy is your incident. Over HTTP that coupling is inseparable from the call, because the response has to arrive while you still hold the socket.</p>