Architecture

Architecture is the set of decisions that determine what a system can and cannot do. Most organisations discover their architecture by observing its constraints.

Architecture — the decisions that determine what a system can and cannot do. Architecture decisions break down into four areas: Scalability (growth capacity and performance under load); Integration (APIs and system connectivity); Maintainability (whether a system is understandable and extendable); and Technical Debt (cost of change and future constraints). These decisions produce outcomes across a four-tier stack, in order: Data Model at the foundation, then Architecture, then Applications, then Infrastructure — each layer building on the one beneath it.

Good architecture is not invisible. It is explicit — documented, understood, and maintained. The systems that are reliable, scalable, and maintainable are the ones that were designed that way. The systems that are fragile, expensive to change, and owned by nobody are the ones that accumulated rather than being designed.

What architecture actually determines

Architecture determines several things that appear later in ways that are difficult to trace back to the original decision.

Scalability ceiling. The architecture determines how far the system can grow before it requires fundamental reconstruction. A system built without scalability as a design input has a ceiling. The ceiling appears under load.

Integration cost. How systems connect to each other is an architectural decision. Integration that was designed as a first-class concern is maintainable and reliable. Integration that was added as an afterthought is expensive to change and fragile under load.

Maintainability. Whether a system can be understood, modified, and extended by people who did not build it is an architectural property. Systems that can only be maintained by their original authors are single points of failure.

Technical debt profile. Every architecture carries some debt — decisions made under constraint that will need revisiting. The architecture determines where the debt is, how much it costs to carry, and how much it costs to resolve.

The approach

Every architecture engagement starts with the data model. The data model is the foundation on which architectural decisions are made. Architecture designed without a properly defined data model inherits the model’s inconsistencies at a structural level.

Start a Conversation