Terminology

2185 terms, tools, patterns and metrics an architect is expected to use precisely. Each one gets a short explanation of what it is, and — where it matters — what it is commonly confused with. Search filters as you type; the column headers sort.

All areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 AI-Era Architecture69 Software Architecture & Engineering71 Architecture Patterns71 Architecture Decision-Making63 The Architect's Meta-Skills61 Delivery & Release Engineering66 Platform Engineering & Developer Experience70 Testing & Quality Architecture66 Data Platform Architecture64 Streaming & Real-Time Data69 Data Governance & Semantics69 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk64

Kind Any concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

24 terms shown.

Term	Kind	Topic	What it is
Build vs Buy	concept	Architecture Decision-Making	The choice between developing a capability in-house and acquiring it, decided on differentiation and total cost rather than on feature lists.
Centralisation Trade-off	concept	Centralised vs Distributed	The exchange between consistency and control gained by centralising a capability and the autonomy and speed retained by distributing it.
Centralised versus Distributed	concept	Centralised vs Distributed	Whether a capability should be one shared thing or many independent ones — a recurring decision whose answer changes with organisation size.
Complexity Budget	concept	Reliability vs Complexity	The idea that an organisation can operate only a bounded amount of complexity, so each resilience mechanism must justify its share.
Correlated Region Failure Shared-Fate Region Dependency, Region Failure Correlation	concept	Single vs Multi-Region	The shared dependencies that make two regions fail together, which is why multiplying regions multiplies cost but adds far less availability than independence arithmetic predicts.
Decision Debt Unrecorded Decision Backlog, Undocumented Choice Accumulation	concept	Decision Practice	The accumulated set of choices a system embodies but nobody wrote down, which turns every later change into an archaeology exercise and makes safe modification depend on individual memory.
Delivery versus Maintainability	concept	Delivery vs Maintainability	Shipping faster now by accepting future cost — a legitimate trade when it is deliberate, recorded and repaid.
Execution Model Fit	concept	Serverless vs Containers	Matching a workload's traffic shape, duration and state requirements to the execution model that suits it, rather than choosing one model for everything.
Expensive-to-Change Core	concept	Delivery vs Maintainability	The small part of a system whose shape is copied into stored data and into other people's code, where a shortcut cannot be repaid locally - so deliberate debt belongs everywhere else.
Friction Budget	concept	Security vs Usability	The limited amount of security friction users will absorb before they work around it, making usability a security property rather than its opponent.
Monolith vs Microservices	concept	Architecture Decision-Making	A trade of deployment independence against distributed-systems complexity, decided by team topology far more often than by technology.
One-Way Door Irreversible Decision, Type 1 Decision, Foreclosed Option	concept	Reversibility	A decision whose reversal is prohibitively expensive or impossible, which is where analytical effort belongs - as distinct from the reversible majority, where deliberation typically costs more than being wrong.
One-Way Door Decision Type 1 Decision, Irreversible Decision	concept	Reversibility	A decision that is very costly or impossible to reverse, warranting deliberation proportionate to that permanence.
Operated Reliability Realised Availability	concept	Reliability vs Complexity	The availability a system actually achieves in the hands of the team running it - as distinct from the availability its topology implies.
Performance versus Cost	concept	Performance vs Cost	The trade between latency and spend — where headroom is the mechanism and high utilisation is the false economy.
Query Surface Volatility	concept	SQL vs NoSQL	How fast a product invents query shapes it did not have before - the workload fact that decides whether a purpose-built physical layout or a general query planner is the cheaper bet.
Reliability versus Complexity	concept	Reliability vs Complexity	Mechanisms added for reliability introduce their own failure modes — so past a point, more machinery makes a system less reliable.
Request-Reply and Fire-and-Forget	concept	Sync vs Async	The two interaction shapes available between components, differing in whether the caller waits for a result and therefore in whether availability compounds.
Reversible Decision Two-Way Door	concept	Architecture Decision-Making	A choice that can be undone cheaply, and which therefore deserves far less deliberation than an irreversible one.
Security versus Usability	concept	Security vs Usability	Controls that impose too much friction get circumvented — so the usable control is frequently the more secure one.
SQL vs NoSQL	concept	Architecture Decision-Making	A choice driven by access patterns, consistency requirements and query flexibility — not by data volume, which is the reason usually given.
Strong vs Eventual Consistency	concept	Architecture Decision-Making	A per-operation decision, not a per-system one: whether this specific read must reflect every completed write.
Synchronous vs Asynchronous Communication	concept	Architecture Decision-Making	Whether the caller waits for the callee's answer — decided by whether the caller's outcome depends on it, not by latency or taste.
Two-Way Door	concept	Reversibility	A decision that can be undone cheaply, and which therefore warrants a fast decision by the people closest to the work rather than extensive analysis.