Terminology
2225 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 areas2225
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 Architecture74
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 Architecture69
Streaming & Real-Time Data69
Data Governance & Semantics74
Frontend & Experience Architecture66
Edge, Mobile & IoT68
Regulatory & Data Protection Architecture65
Assurance, Audit & Model Risk69
4 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Mobile App Architecture | concept | Mobile App Architecture | Client architecture where the release cycle is not yours, old versions persist indefinitely, and the network is unreliable. |
| Platform Lifecycle Constraint | concept | Mobile App Architecture | The operating system's rules about when your process runs, which are not negotiable and invalidate most assumptions carried over from server code. |
| Store-and-Forward Queue On-Device Send Queue, Deferred Send Buffer | pattern | Mobile App Architecture | A durable queue on the device that accepts writes while the network is absent and drains them in order when it returns - with an explicit policy for what happens when it fills or an entry is rejected. |
| Untrusted Client Timestamp Device Time Is Not Authoritative, Client Clock Assumption | concept | Mobile App Architecture | The recognition that a timestamp set by a device is user-editable input rather than a fact - so reporting periods, ordering and de-duplication must not depend on it. |
Nothing on this page matches. Search the whole glossary.