OakfieldCore
← Research journal

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.

Ownership plan diagram
Ownership plan

Follow the disputed fact

Consider a booking that is visible in a calendar while its payment is still pending. A calendar entry and a confirmed reservation can look identical on a screen. They carry different promises. Splitting the booking and payment code into separate services will not settle which promise the customer received.

Begin with a sentence that someone can challenge: a reservation exists once capacity has been allocated. Identify the component allowed to make that statement. The payment component may provide evidence, but it cannot allocate the final place unless it also owns the capacity rule.

Name the interval

Draw the interval between allocation and confirmation. What may a reader display during that interval? Can the customer cancel? If a timeout occurs, which action releases the allocation? These questions reveal where apparent agreement in a diagram hides a disagreement in behaviour.

Give the intermediate state a specific name and a route to completion. A held place might carry an expiry time owned by the reservation component. A payment acknowledgement can then be handled as an input to that state machine, including when it arrives after expiry.

Use a counterexample in review

Walk two requests through the model for the last available place. Interrupt the first request immediately after its write. If the second can claim the place because it reads a delayed view, the diagram has exposed a contract that the data model cannot honour.

Keep the example beside the boundary definition. It gives future changes a concrete review question: can two independent writers now make conflicting promises? That question remains useful even when deployment topology, libraries and interfaces change.

Back to the journal