Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
33 results for “Domain Boundaries”
Domain-Driven Design
Modelling software around the business domain, with boundaries drawn where the language of the business changes.
Uber's Domain-Oriented Microservice Architecture
After growing to roughly 2,200 microservices, Uber grouped them into domains behind gateways with strict dependency layering, to recover the comprehensibility that fine-grained de…
Anti-Corruption Layer
A translation layer that converts a legacy or external system's model into your own, so its concepts do not leak into your domain.
Cognitive Load
The total amount a team must hold in its head to work effectively, and a real constraint on how many services or domains one team can own.
Cohesion
The degree to which everything inside one component belongs together and changes for the same reason.
Conway's Law
Systems tend to mirror the communication structure of the organisation that builds them.
DNS
The distributed directory that resolves names to addresses, and a surprisingly load-bearing part of most architectures.
Data Mesh
An organisational approach that gives domain teams ownership of their analytical data as a product, with a self-serve platform and federated governance.
Data-Flow Diagram
A diagram of how data moves between processes, stores and external entities, with trust boundaries drawn on it.
Database per Service
Each service owning its own datastore, with no other service reading or writing it directly.
Encapsulation
Keeping a component's state private, so it can only be changed through operations that maintain its invariants.
Event Store
An append-only store of domain events organised into per-entity streams, serving as the system of record rather than as a log beside it.
Hexagonal Architecture
Putting the domain at the centre and letting everything external — UI, database, queues — attach through ports implemented by replaceable adapters.
Layered Architecture
Organising code into horizontal layers — presentation, application, domain, data — where each layer may only call the one beneath it.
Modular Monolith
A single deployable unit internally partitioned into modules with enforced boundaries, explicit interfaces and no shared internal state.
Modularity
The degree to which a system is composed of parts that can be understood, changed and replaced independently.
Read Model
A data structure shaped for a specific query rather than for the domain, maintained separately from the write model.
Service Boundary
The line separating what one service owns and is accountable for from what it must ask another service about.
Threat Modelling
A structured exercise that identifies what can go wrong with a design, before it is built, by walking the system's trust boundaries.
A team shows you a design with eight services. Without knowing the domain, what questions tell you whether the boundaries are right?
What the interviewer is testing Whether you can evaluate a structure from its properties rather than needing to be a domain expert in every system you review. T
Uber reached roughly 2,200 microservices and found the estate incomprehensible. Their fix was not consolidation. What was it, and why does it generalise?
What they did Uber's 2020 publication on Domain Oriented Microservice Architecture describes three structural rules layered on top of the existing services — no
Domain Boundaries
Where the language of the business changes, and services should too.
Domain-Driven Design
Ubiquitous language, bounded contexts and context mapping.
Service Boundaries
Drawing lines along change patterns rather than technical layers.
Agent Architectures
Loops, planning, memory and the boundaries an agent must not cross.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
Auditability
Tamper-evident, attributed records that survive async boundaries.
Data-Flow Diagrams
Following the data across trust boundaries rather than the calls.
Hexagonal Architecture
Ports defined by the domain, adapters supplied by infrastructure.
Identity & Access Management
Workload identity, roles, permission boundaries and usage-based review.
Modular Monolith
Enforced internal boundaries without a network between them.
Threat Modelling
Walking trust boundaries with STRIDE before anything is built.