OakfieldCore

Independent engineering studio

Systems
built to
endure.

Architecture, platforms and software for systems that need to keep working as they change.

Explore expertise
System anatomyFig. A
Exploded assembly showing three modular decks around a shared red core
Exploded assembly
Studio disciplines

Areas of
practice.

01

Systems Architecture

Where does responsibility sit?

↗
02

Platform Engineering

What should the platform make easy?

↗
03

Software Development

Which behaviour must survive a change?

↗
04

Technical Consulting

Which decision needs evidence?

↗
Engineering position

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 methodology

From the journal

Research notes.

Ownership plan diagram
Ownership plan
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.

↗
Queue and consumers diagram
Queue and consumers
Scalability

Queues have edges

A queue can absorb a burst. Its limits become visible when work arrives faster than consumers can finish it.

↗
Decision loop diagram
Decision loop
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.

↗