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
794 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Shared Responsibility Model | concept | Managed Services | The division of duties between provider and customer, which shifts with the service model and is routinely misunderstood in the customer's disfavour. |
| Shared Singleton Skew Duplicate Framework Instance, Singleton Version Mismatch | concept | Module Federation | The failure class created when independently built front-end bundles expect different versions of a library that must exist once per page, producing either incompatible reuse or two isolated copies that share … |
| Shared-Service Commons Free-at-Point-of-Use Platform, Uncharged Internal Platform | concept | Showback & Chargeback | The failure mode where cost allocation prices each team's own resources but leaves internal platforms free to use, so teams move cost onto the shared estate instead of removing it and total spend rises while e… |
| Shared-Team Queue Central Team Bottleneck, Review Queue | concept | Operating Models | The queueing behaviour of any central team that must approve or perform work for many others, where waiting time rises sharply as utilisation approaches capacity and teams begin routing around the control. |
| Sidecar Interception Boundary Mesh Coverage Boundary, Proxy Capture Scope | concept | Sidecar & Ambassador | The precise set of traffic a sidecar proxy actually sees and can secure, which is narrower than "all traffic from this pod" and is what decides whether a mesh's guarantees apply to a given call. |
| Sidecar Resource Overhead | concept | Sidecar & Ambassador | The cumulative CPU, memory and latency cost of running helper containers alongside every application container. |
| Silent Coercion Type Coercion on Ingest, Quiet Data Corruption | concept | Ingestion Patterns | An ingestion pipeline converting a value it did not expect rather than rejecting it - the worst available failure mode, because the load succeeds and the data is wrong downstream with nothing indicating it. |
| Silent Control Failure Dormant Control, Control Decay | concept | Control Design vs Operation | A control that has stopped operating while still reporting success, so the organisation keeps making decisions on the assumption that it is protecting them. |
| Silent Data Failure No Error, Plausibly Wrong, Quiet Breakage | concept | Data Observability | A data problem that produces no error - the pipeline succeeded, the schema was valid, the numbers were plausible - which is why error-based monitoring cannot detect it and why it persists for weeks. |
| Silent Quality Regression Payload-Level Degradation, Unasserted Output Failure | concept | Failure Thinking | A defect that leaves status codes, latency and throughput normal while making the content of responses worse - so every envelope-level alert stays green and the only available signal is statistical. |
| Six Rs of Migration 6 Rs, Migration Strategies | concept | Legacy Modernization | The standard menu of options for each application in a migration — rehost, replatform, refactor, repurchase, retire, retain. |
| SLA Measurement Point Measurement Boundary, Observation Point | concept | Negotiation | The place in the request path where an availability or latency commitment is observed, which decides what the number means and is where nearly every SLA dispute actually originates. |
| Small File Problem | concept | File Formats & Compaction | The severe query degradation caused by a table stored as very many tiny files, where per-file overhead dominates actual data reading. |
| SOLID Principles | concept | SOLID | Five object-design principles whose architectural value lies almost entirely in the last one — dependency inversion. |
| Solution Architecture | concept | Architecture Fundamentals | The design of a specific system that satisfies a specific business problem under a specific set of constraints. |
| Source NAT SNAT, Masquerading | concept | NAT & Egress | Rewriting the source address of outbound packets so that many private addresses share one public address, with a translation table mapping replies back. |
| Span Link Trace Link, Span Reference | concept | Distributed Tracing | A pointer from one span to another span in a different trace, recording a causal relationship where no single enclosing parent exists - the mechanism that keeps batch jobs, fan-in consumers and delayed asynchr… |
| Speculative Abstraction Premature Abstraction, Anticipatory Design | concept | Design Patterns | Structure added for variation that has not occurred - paying certain indirection now for a benefit that depends on a guess about the future. |
| Split Brain | concept | Leader Election | A partition in which two subsets of a cluster each believe they are authoritative, accepting conflicting writes that cannot afterwards be reconciled. |
| Split Vote | concept | Leader Election | An election in which no candidate obtains a majority, so the term ends with no leader and the process must repeat. |
| SQL Transformation Model | concept | Transformation Frameworks | A named, versioned, tested SELECT statement that declares its own dependencies, turning transformation logic into reviewable software. |
| 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. |
| Standardisation Blast Radius Monoculture Exposure, Standard Concentration | concept | Technology Standards | The property that a technology standard concentrates exposure as well as capability - one flaw in the standardised component applies to the whole estate - which turns the ability to change it everywhere at sho… |
| Standing Credential Long-Lived Credential, Persistent Secret, Static Key | concept | Secrets Management | A credential that remains valid indefinitely, so a single leak grants permanent access - the property that converts a small compromise into a large one, and the one a secrets manager does not fix. |
| Stateful Packet Filtering | concept | Firewalls & Security Groups | Filtering that tracks connection state, so return traffic for an allowed outbound connection is permitted automatically. |
| Stateful Stream Processing | concept | Stateful Stream Processing | Stream computations that must remember information across events — aggregations, joins, deduplication, sessionisation — and the durability machinery that makes them recoverable. |
| Static Stability Fail Static, Configuration Inertia, Control-Plane Independence | concept | Cloud Architecture | Designing a system so it continues operating correctly on its existing configuration during a failure, requiring no control-plane action to survive - because control planes are the part most likely to be unava… |
| Static Stability Stability Under Failure | concept | Static Stability | A system that keeps working correctly in its current state when its control plane or dependencies become unavailable, rather than needing them to stay running. |
| Steady-State Hypothesis | concept | Chaos as a Test | The measurable statement of normal behaviour that a chaos experiment predicts will hold while a fault is injected, without which the exercise is not a test. |
| Storage Costs | concept | Storage Costs | Storage is cheap per gigabyte and expensive in aggregate — controlled by retention and tiering rather than by unit price. |
| Stream-Table Duality | concept | Stream-Table Duality | The equivalence between a stream of changes and a table of current state, where each can be derived from the other. |
| Streaming Cost Model | concept | Streaming Cost | The cost structure of an always-on streaming system, where compute runs continuously regardless of volume and cross-zone data movement is a major line item. |
| Streaming Data Architecture | concept | Streaming Data | Processing unbounded data continuously, where the central problems are time semantics, lateness and state rather than throughput. |
| Streaming Join | concept | Streaming Joins | Combining two streams, or a stream and a table, where the records to be joined may not arrive at the same time or in the same order. |
| 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. |
| Style versus Pattern | concept | Architecture Styles | The distinction between a system-wide organising structure and a reusable solution to a recurring problem within it. |
| Subagent Context Isolation Parallel Context Windows, Context Partitioning Across Agents | concept | Multi-Agent Systems | The property that makes multi-agent systems worth their cost - each subagent explores with its own context window and returns only a condensed result, so the system reads far more than one context could hold. |
| Subject Naming Strategy | concept | Schema Registry | How schemas are keyed in a registry — per topic, per record type, or both — which determines whether one topic may carry several event types. |
| Submission Deadline Architecture | concept | Regulatory Reporting Pipelines | Designing a reporting pipeline around a fixed external deadline, where late is a breach and the recovery window is part of the schedule rather than a contingency. |
| Subnet | concept | Networking | A subdivision of a network's address range, used as the unit of routing and, in cloud, of availability-zone placement. |
| Suite Reliability Arithmetic Per-Test Flake Rate Derivation, Suite Green-Rate Calculation | concept | Testing Strategies | The calculation that turns a suite's target green rate and its test count into the per-test flake rate each test must meet, which is what determines how many high-level tests a team can afford to have at all. |
| Surrogate Key Synthetic Key | concept | Relational Modelling | A system-generated identifier with no business meaning, used as the primary key instead of a naturally occurring business value. |
| Symptom-Based Alerting Alert on Effects, User-Visible Alerting | concept | Alert Fatigue | Paging on what the user experiences and investigating causes with dashboards - because cause-based alerts fire in clusters during a single incident and bury the signal they exist to provide. |
| Sync Conflict Resolution | concept | Sync & Conflict Resolution | The policy applied when the same record was changed on two devices while they were disconnected, and both changes now arrive. |
| 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. |
| Synchronous vs Asynchronous Replication | concept | Replication | Whether a write is acknowledged only after a replica has it, trading write latency against the amount of data a failure can lose. |
| Synthetic Data Fidelity | concept | Synthetic Data | How closely generated data reproduces the shape, distribution and awkwardness of the real thing, which decides what the data can validly be used for. |
| System Context Boundary | concept | Context Diagrams | The line separating what a project owns and can change from what it must integrate with and accept as given. |
| System of Record Authoritative Source, Golden Source | concept | EA Domains | The single system authoritative for a business entity, from which all other copies derive - the absence of which is the dominant source of enterprise complexity. |
| Table Bootstrap Lag Join Side Warm-Up, Lookup State Load Time | concept | Streaming Joins | The interval after a stream job starts during which its lookup table is only partly loaded, so enrichment lookups miss for keys that appear late in the source topic and the job emits wrong output while looking… |
| Tail Composition Effect Fan-Out Tail Amplification, Page-Level Tail | concept | Tail Latency | The multiplication that turns a small per-request slow rate into a large user-visible slow rate, because a single user action makes many requests and is only as fast as its slowest one. |
| Tail Latency Amplification Fan-out Tail, Slowest-Component Latency | concept | Tail Latency | A parallel fan-out completes when its slowest component does, so ordinary per-component tails combine into a much worse end-to-end tail. |
| Tail Latency Amplification | concept | Tail Latency | The effect where a request that fans out to many services experiences the worst case of all of them, making rare slowness common at the user level. |
| Target-State Decay Architecture Plan Decay, Target Architecture Drift | concept | Architecture Roadmaps | The rate at which an approved target architecture stops being correct - mostly for organisational reasons rather than technical ones - and the reason a plan with no review date turns into a set of case-by-case… |
| Team Interaction Mode | concept | Team Topologies | The defined way two teams work together — collaborating, consuming a service, or facilitating — chosen deliberately and expected to change over time. |
| Team Topologies | concept | Team Topologies | Four team types and three interaction modes, used deliberately to shape both the organisation and the architecture it produces. |
| Technical Constraints | concept | Technical Constraints | The existing estate, skills, licences, contracts and platforms that bound the solution space — inputs to the design, not obstacles to it. |
| Technical Debt | concept | Software Architecture | The future cost incurred by choosing an expedient implementation now instead of the better one. |
| Technical Debt Quadrants | concept | Technical Debt | Distinguishing debt by whether it was taken deliberately or inadvertently, and prudently or recklessly, since the four kinds need different responses. |
| Technology Architecture | concept | Technology Architecture | The platforms, infrastructure and runtimes the estate depends on — where the recurring architectural problem is obsolescence rather than choice. |
Nothing on this page matches. Search the whole glossary.