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
9 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Content Pre-Positioning Proactive Fill, Push CDN, Predictive Caching | pattern | Content Delivery Networks | Pushing predicted-demand content to edge caches during off-peak hours rather than fetching it on first request, converting an unpredictable peak-time origin fetch into a scheduled transfer when capacity is free. |
| Cost-Weighted Rate Limiting Compute Units, Weighted Quotas | pattern | API Gateways | Limiting callers by the resources their requests consume rather than by request count, because on any API where request cost varies by orders of magnitude, counting requests protects nothing. |
| Gateway Offloading | pattern | API Gateways | Moving cross-cutting concerns — TLS termination, authentication, rate limiting, compression, logging — from every service into the gateway. |
| Origin Shield Shield Tier, Mid-Tier Cache, Request Collapsing Tier | pattern | Reverse Proxies | An intermediate caching tier between edge caches and the origin that collapses many simultaneous misses into a single origin fetch - which is what makes multi-CDN and live streaming survivable for the origin. |
| Progressive Media Materialisation Lazy Transcoding, On-Demand Rendition | pattern | Content Delivery Networks | Generating only a baseline media rendition on upload and producing higher-quality variants on first demand - trading a slower first view of unpopular content for a large reduction in transcoding and storage cost. |
| Reverse Proxy | pattern | Networking | A server that receives client requests on behalf of one or more backends, forwarding them and returning the response. |
| Reverse Proxy in Practice | pattern | Reverse Proxies | A server that sits in front of origins and terminates, caches, routes and protects — the cheapest place to solve several problems at once. |
| Traffic Splitting | pattern | Service Mesh Networking | Directing a defined percentage or subset of requests to a different version of a service, configured at the routing layer rather than in application code. |
| WebSocket Backplane | pattern | WebSockets & Realtime | A shared publish/subscribe layer letting a message published on one server reach clients connected to a different server. |
Nothing on this page matches. Search the whole glossary.