Terminology

2205 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 areas2205 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture86 Cost Architecture & FinOps71 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization71 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 concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

3 terms shown.

Term	Kind	Topic	What it is
Per-Entity Migration State Record-Level Ownership Flag, Entity Migration Flag, Per-Row Routing State	pattern	Coexistence Patterns	A field on each business entity naming the system currently authoritative for it, which makes the unit of migration one row rather than one capability - so traffic moves in nameable cohorts and rolls back by u…
Reverse Replication Cutover Backflow Replication, Bidirectional Cutover Window, Rollback Stream	pattern	Coexistence Patterns	Keeping a replication stream flowing from the new store back to the old one after writes have moved, so that rolling back stays a routing change instead of a restore from backup.
Write-Ownership Boundary Single-Writer Boundary, Authoritative Writer Assignment	pattern	Coexistence Patterns	The line drawn during coexistence that names exactly one system as the writer for each piece of state, placed along business transaction boundaries so that no single transaction has to commit on both sides.