Terminology

2240 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 areas2240 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience80 Observability75 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 Architecture71 Data Platform Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept806 practice738 pattern379 metric133 case-study77 tool62 protocol45

2240 terms shown.

Term	Kind	Topic	What it is
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.
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.
Technical Depth Calibration	practice	Presenting to Engineers	Matching the level of detail and the mode of engagement to an engineering audience, which needs reasoning and the opportunity to disagree.
Technical Leadership	practice	Technical Leadership	Setting technical direction and raising the standard of decisions across an organisation — largely without authority and largely through other people.
Technical Proposal Design Doc, RFC	practice	Architecture Communication	A written argument for a course of action, circulated for review before the work starts, structured so that disagreement surfaces early and cheaply.
Technical Proposal Structure	practice	Technical Proposals	An arrangement for a written design proposal that lets reviewers engage with the decision rather than reconstructing the problem.
Technology Architecture	concept	Technology Architecture	The platforms, infrastructure and runtimes the estate depends on — where the recurring architectural problem is obsolescence rather than choice.
Technology Evaluation Criteria	practice	Technology Selection	A standing set of dimensions for assessing a candidate technology, ensuring that operability and longevity are weighed alongside capability.
Technology Radar	tool	Technology Radar	A published, periodically revised classification of technologies into adopt, trial, assess and hold, giving guidance without issuing a mandate.
Technology Selection	practice	Technology Selection	Choosing a technology on the basis of fit, operability and organisational capacity — with a strong prior toward what you already run well.
Technology Stack Standardisation	practice	Technology Architecture	Converging on a supported set of platforms, languages and tools to reduce operational surface, while allowing justified exceptions.
Technology Standards	practice	Technology Standards	Constraining technology variety to reduce operational cost — with a waiver path, or the standard is broken quietly rather than formally.
Telemetry Cost Control	practice	Telemetry Cost	Managing the spend on logs, metrics and traces, which in mature estates can approach or exceed the cost of the infrastructure being observed.
Telemetry Cost Management	practice	Telemetry Cost	Controlling observability spend through sampling, retention tiering and cardinality limits without losing diagnostic capability.
Telemetry Pipeline Lag Ingestion Delay, Time to Queryable, Observability Freshness	metric	Observability	The delay between an event being emitted and being queryable, which bounds how quickly any decision made from telemetry can respond to reality.
Telemetry Sampling	practice	Observability	Keeping a subset of traces or events to bound observability cost, chosen so the ones that matter survive.
Telemetry Spend Ratio	metric	Observability Cost	Observability cost as a proportion of the infrastructure it observes, used as a tripwire for a category that grows silently.
Template Propagation Getting Improvements Into Existing Services, Template Drift	practice	Service Templates	The mechanism by which improvements to a service template reach the services already generated from it - the hardest part of the template model and the part most often omitted.
Temporal Coupling	concept	Coupling	A dependency in which one component requires another to be available at the same moment, so the availability of both is required for either to work.
Temporal Join As-Of Join, Point-in-Time Join	pattern	Streaming Joins	A join that enriches an event with the reference value as it was when the event occurred, rather than as it is now - which is the difference between a reproducible result and a drifting one.
Tenant Placement Hybrid Tenancy, Shared-to-Dedicated Migration	pattern	Partitioning & Sharding	Routing each tenant to a shared pool or a dedicated database according to its size and requirements, with an online migration path between them - the hybrid model that neither all-shared nor all-dedicated can match.
Tenant-Scoped Layout Key Tenant Clustering Key, Tenant-Aligned Physical Layout	pattern	Data Platform Tenancy	Making the tenant identifier the column that governs a table's physical organisation, so isolation, per-tenant cost attribution and per-tenant deletion come from layout rather than from access control alone.
Term Definition Ownership	practice	Business Glossary	Assigning one accountable owner per business term, so that a disagreement about meaning has a route to resolution rather than a standing argument.
Terraform State IaC State File	concept	Infrastructure as Code	The file mapping declared resources to real infrastructure, without which the tool cannot tell what it already created — and which becomes critical infrastructure in its own right.
Test Architecture Strategy	practice	Test Architecture Strategy	A written decision about which risks are covered by which kind of test, at what scope, run at what point, and which risks are accepted.
Test Data Management	practice	Test Data Management	The problem of getting data that is realistic enough to find defects and safe enough to exist outside production.
Test Data Provisioning	practice	Test Data Management	Getting each test the data it needs, in a state it can rely on, without copying production personal data into a weaker environment.
Test Double Stub, Mock, Fake, Spy	concept	Service Virtualisation	Any stand-in for a real collaborator in a test - and the five kinds differ in what they let you assert, which is why using the wrong one produces tests that break on refactoring or pass while the code is wrong.
Test Double Boundary	concept	Integration Test Boundaries	The line inside a test between what is real and what is substituted, which determines exactly what the test can and cannot prove.
Test Pyramid	pattern	Test Pyramid Shapes	The heuristic that a suite should hold many fast isolated tests, fewer integrated ones, and very few full end-to-end tests.
Test Quarantine Flaky Test Isolation	practice	Flaky Test Management	Removing an unreliable test from the blocking suite immediately, so it stops eroding trust, while keeping it running non-blocking until it is fixed or deleted.
Test Strategy Altitude	concept	Testing & Quality Architecture	Deciding which risks are verified at which level, so that each layer tests something the layers below it structurally cannot.
Test-Owned Data Data Created By The Test, Per-Test Tenancy	pattern	Test Data Management	Each test creating the exact data it needs through the product's own write path and disposing of it afterwards - replacing shared fixtures whose drift and coupling cause most cross-team test failures.
Testability Design for Test	concept	Testing & Quality Architecture	The architectural property that determines what kinds of test are possible - which decides the shape of the suite far more than any testing discipline does.