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
5 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Additive-Only Evolution Non-Breaking Change Discipline, Tolerant Reader Contract | concept | API Versioning | Establishing the compatibility contract before the first release - unknown fields ignored, unknown enum values defaulted - so that most future change requires no version at all. |
| API Versioning Strategy | practice | API Versioning | The scheme for introducing incompatible change, and the far more important question of how long old versions live and who pays to migrate. |
| Semantic Versioning SemVer | practice | API Versioning | A version scheme where the number itself states the compatibility promise — major for breaking, minor for additive, patch for fixes. |
| Stripe: Versioning by Account Pinning Stripe API Versions | case-study | API Versioning | Stripe pins each account to the API version it first integrated against and maintains compatibility transformations, so integrations built years ago continue to work unchanged. |
| Version Transformation Layer Version Shim, Compatibility Transform, Request/Response Rewriting | pattern | API Versioning | Implementing an API once against its current shape and expressing every historical version as a pair of request and response transformations, so supporting an old version costs a small testable function rather… |
Nothing on this page matches. Search the whole glossary.