8861 Lab

Latest — 16 Mar 2026

Business Provides Clarity. Product Writes Contracts. Engineering Implements Them. Infrastructure Makes It Real

Relative Architecture works in practice when four distinct roles are fulfilled. They may be inhabited by one person or many, by existing teams or new ones. What matters is that the responsibilities each role carries are clearly owned. The four roles are Business, Product, Engineering, and Infrastructure. Business, Product, and

More issues

The Phone Calls Were Always This Model

The responsibilities never changed. The medium did. Understanding why a responsibility-based architecture matters now requires understanding how business integration has evolved across three generations. Not three generations of technology — three generations of how organisations actually fulfill their responsibilities and connect them to each other. Generation 1 — Analog Internal Organisations fulfilled

The Event Contract Is the Only Boundary That Matters

Why the schema of what your system publishes is more architecturally significant than the framework it runs on, the database it uses, or the team that built it. There is a thought experiment worth doing before designing any distributed system. Imagine you need to replace one of your services completely.

Orchestration and Choreography Are Not Opposites

They operate at different levels of the same system. Choosing between them is a false dilemma that produces worse architectures than understanding why both exist. Every serious distributed systems discussion eventually arrives at the same question. Should we orchestrate or choreograph? The canonical answer is that you should pick one

More issues

Subscribe to 8861 Lab