Portfolio ↗

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

2205 terms shown.

Term Kind Topic What it is
Stress Test practice Stress Testing Driving load beyond expected capacity to observe how the system behaves at and past its breaking point.
Stress Testing practice Stress Testing Deliberately exceeding capacity to find where the system breaks and — more importantly — how.
STRIDE practice Threat Modelling A mnemonic for six threat categories — spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege — walked across each component and data flow.
Stripe Webhooks: Delivering to Systems You Do Not Control Signed Webhooks case-study Webhooks Outbound event delivery to arbitrary customer endpoints requires signing, retries over days, explicit at-least-once semantics and a replay interface.
Stripe's API Versioning case-study API & Integration Stripe pins each account to the API version current when it integrated and transforms requests and responses between versions internally, so integrations never break and the core stays modern.
Stripe: Idempotency Keys as a Public API Contract Idempotency-Key Header case-study Idempotency Keys Stripe made safe retry a documented, client-controlled property of its API, which is why network failures during payments do not produce duplicate charges.
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.
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.
Structural Cost Attribution Boundary-Based Allocation, Attribution Without Tagging practice Cost Allocation Deriving cost ownership from deployment boundaries - account per workload, cluster per team - rather than from tags, because tagging discipline never survives contact with a growing organisation.
Structured Logging practice Structured Logging Emitting logs as machine-parseable key-value records rather than formatted prose, so they can be queried, aggregated and correlated.
Style versus Pattern concept Architecture Styles The distinction between a system-wide organising structure and a reusable solution to a recurring problem within it.
Sub-Capacity Licensing Virtualisation Capacity Licensing, Sub-Capacity Entitlement practice Licence & Vendor Costs The vendor programme that allows a per-core licence to be counted against the cores a workload is actually allowed to use, which is conditional on approved metering and reverts to the whole host when the meter…
Sub-Second Aggregation Store tool Real-Time Analytical Stores A database built to ingest continuously and answer aggregate queries over recent data in milliseconds, occupying the gap between OLTP and the warehouse.
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 Access Fulfilment practice Data Subject Rights The operational path from a request to a complete, verified, delivered response within the statutory period, across systems that were never designed for it.
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.
Subnet Sizing practice Subnetting Choosing subnet prefix lengths with enough headroom, given that subnets cannot be resized and cloud providers reserve several addresses in each.
Subnetting and Address Planning practice Subnetting Dividing address space across zones and tiers, and the exhaustion failures that appear only at container density.
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.
Superseded-Work Cancellation Build Cancellation, Queue Deduplication practice Containers Cancelling queued work that a later submission has made irrelevant - usually the largest single capacity saving available during a burst, and almost free to implement.
Supply Chain Attestation SLSA, Provenance Attestation practice Supply Chain Security A signed statement about how an artifact was produced — from which source, by which builder, with which inputs — verified before deployment.
Supported Path Maintenance Load Golden Path Upkeep Cost, Path Matrix Load metric Paved Road & Golden Path The recurring engineering cost of keeping every supported path working against every change in the platform beneath it, which is what actually caps how many paths a platform can offer.
Suppression List Do-Not-Reprocess List, Erasure Tombstone Registry pattern Data Subject Rights A durable record of identifiers that must not be re-ingested, preventing an in-flight or replayed pipeline from recreating data that was just erased.
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.
Survivorship Rules Golden Record Rules, Attribute Precedence practice Master Data Management Per-attribute rules deciding which source's value wins when several systems hold a different value for the same entity - the part of master data management that determines whether the golden record is trusted.
Sustainable On-Call practice On-Call An on-call arrangement whose alert volume, rotation size and compensation allow it to continue indefinitely without degrading the people in it.
Switching Egress Waiver Exit Transfer Credit, Egress Waiver on Exit practice Network & Egress Costs The provider programme that removes data-transfer-out charges for a customer leaving the platform, which deletes the headline number in most exit business cases and leaves engineering time and dual-running as …
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.
Sync Engine Local-First Sync, Client Database Replication, Delta Sync pattern Modular Monolith A client-side database kept continuously in sync with the server through deltas, so every read and write is local and instantaneous - moving the network off the interaction critical path entirely.
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 tool Synthetic Data Artificially generated data that preserves the statistical and structural properties of real data without containing anyone's actual records.
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.
Synthetic Monitoring practice Testing in Production Continuously executing a real user journey against production from outside it, so a broken journey is detected before a user reports it.
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.
Systems Thinking practice Meta-Skills Reasoning about a system in terms of the interactions and feedback loops between its parts, rather than the parts individually.
Systems Thinking in Architecture practice Systems Thinking Reasoning about a system as a set of interacting feedback loops rather than as a collection of components, so that second-order effects are anticipated.
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…
Table Maintenance Budget Maintenance Capacity Reservation, Housekeeping Window practice Workload Isolation Treating compaction, clustering and snapshot expiry as a workload class with its own reserved compute and a guaranteed window, rather than as low-priority work that loses to every deadline.
Tabletop Exercise practice Game Days A discussion-based walkthrough of a hypothetical incident that tests procedures and decision-making without touching any system.
Tag-Bound Access Policy Classification-Driven Access Control, Tag-Based Masking pattern Data Classification An access rule attached to a classification label rather than to a table, so that tagging data is what applies the control and derived copies inherit it through lineage.
Tagging Strategy practice Cloud Governance A defined, enforced set of metadata labels applied to every resource, without which cost allocation, ownership and lifecycle automation are all impossible.
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 p99, p999 metric Performance & Capacity The latency experienced by the slowest small percentage of requests, which is what users and dependent services actually feel.
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.
Tail-Based Sampling Post-Trace Sampling, Intelligent Sampling practice Sampling Deciding whether to keep a trace after it completes, so that errors and slow requests are always retained while ordinary traffic is sampled cheaply.
Tamper-Evident Log pattern Auditability An audit log constructed so that any modification or deletion of past entries is detectable, typically by chaining entries cryptographically.
Target Tracking Scaling pattern Autoscaling An autoscaling policy that adds or removes capacity to hold a chosen metric near a target value, like a thermostat, rather than reacting to threshold breaches.
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…
TCP Handshake protocol TCP/IP The three-way SYN / SYN-ACK / ACK exchange that establishes a TCP connection, costing one round trip before any data moves.
TCP/IP protocol Networking The layered protocol suite underneath essentially all application traffic — IP routes packets, TCP turns them into a reliable ordered stream.
TCP/IP for Architects protocol TCP/IP What an architect actually needs from the transport layer — handshake cost, congestion behaviour, head-of-line blocking, and when to abandon TCP entirely.
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.