Reference Models
Shared conceptual frames — layering, tiers, viewpoints — and their limits.
4 to work through
-
intermediate
A B2B procurement platform adopts an industry reference model for its catalogue and order domain. When does that help, and when does it become a liability?
1 min answer -
intermediate Multiple choice
A team adopts a cloud vendor's reference architecture wholesale to run two containers and a database. The result is a hub-and-spoke network with a firewall appliance and three subscription boundaries. What went wrong?
2 min answer -
intermediate
A travel platform is building its third availability-and-pricing integration in two years, each with a different internal shape. An architect proposes a reference model. What should it contain to be useful, and what makes reference models fail in practice?
2 min answer -
advanced
Four years ago a platform team adopted a cloud vendor's landing-zone reference architecture whole: hub-and-spoke network, three subscription tiers, a central firewall appliance, a shared CI account. The estate turned out to be three products and 40 engineers. The appliance adds a 12 ms hop to every internal call and caused two of the last five incidents. Auditors were told the architecture "conforms to the vendor reference". Sequence the migration to a simpler topology without losing the audit story.
3 min answer
3 terms in this topic
Capability Model
A structured map of what a business does, independent of how it is organised or which systems support it, used to align technology investment with fu…
conceptReference Model
A shared conceptual frame — layers, tiers, viewpoints, capability maps — that gives a conversation vocabulary, and whose limits are frequently forgotten.
practiceReference Model Tailoring
Recording which elements of an adopted reference model you kept, replaced or dropped and why, so a deliberately smaller architecture stays defensible…
Neighbouring topics
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Requirements to Constraints
Turning stated requirements into the constraints that actually bound a design.
Functional vs Non-Functional
Behaviour versus quality of behaviour, and why only the second constrains structure.
Architectural Drivers
The small subset of requirements whose change would force the structure to change.
Quality Attributes
Availability, latency, throughput, security, cost — expressed as testable scenarios.
Architecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
Coupling
How much one component must know about, or change alongside, another.
Cohesion
Whether the things inside a boundary belong together and change for the same reason.
Modularity
Composing a system from parts that can be understood and replaced independently.
Separation of Concerns
Organising so that a change to one concern touches one place.
Abstraction & Encapsulation
Hiding mechanism behind contract, and protecting invariants by owning state.
Architecture Styles
System-level organising shapes, and how they differ from problem-level patterns.
Evolutionary Architecture
Designing for guided incremental change rather than for correctness on day one.
Fitness Functions
Automated checks that an architectural characteristic still holds.
Architecture Documentation
What to write down, at what altitude, and what nobody will ever read.
Conway's Law
Systems mirroring the communication structure of the organisation that builds them.
Trade-off Fundamentals
Why every architecture is a set of purchases, and how to state what you gave up.
Technical Constraints
Existing estate, skills, licences and platforms as inputs rather than obstacles.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.