Independent engineering studio
Systems
built to
endure.
Architecture, platforms and software for systems that need to keep working as they change.
Explore expertiseSystem anatomyFig. A
Studio disciplinesAreas of
Areas of
practice.
Design the boundary.
Then test the crossing.
Follow a single request through an interface, a state change and a recovery. The places where responsibility shifts tell us more about a system than its component list.
Read our methodologyFrom the journal
Research notes.
Architecture
↗Ownership before boundaries
An ownership map begins with a disputed fact. Work out who can declare it true before deciding where to put the interface.
Scalability
↗Queues have edges
A queue can absorb a burst. Its limits become visible when work arrives faster than consumers can finish it.
System design
↗Design for the second request
When a reply disappears, the caller and the service hold different evidence. A retry needs an explicit meaning.