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
734 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| 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. |
| 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 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 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 Sampling | practice | Observability | Keeping a subset of traces or events to bound observability cost, chosen so the ones that matter survive. |
| 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. |
| 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. |
| 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 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. |
| Testing in Production TIP | practice | Testing in Production | Deliberately validating behaviour against real traffic, data and scale, using controls that bound the blast radius. |
| Testing Strategies | practice | Testing Strategies | Choosing what to test at which level, optimising for confidence per unit of time and maintenance rather than for coverage. |
| Third-Party Risk Assessment Vendor Risk, Supplier Assurance | practice | Third-Party Risk | Evaluating the security, resilience and compliance posture of suppliers whose failure would become your incident. |
| Third-Party Script Governance Page as an Execution Environment, Vendor Script Review | practice | Frontend Security | Reviewing and constraining what executes on a page, because every third-party script runs with the page's full privileges - and each one is added individually while the aggregate determines the security posture. |
| Threat Modelling | practice | Security Architecture | A structured exercise that identifies what can go wrong with a design, before it is built, by walking the system's trust boundaries. |
| Time to First Success Time to Hello World, Onboarding Latency | practice | Platform Adoption | How long it takes a new team to get something working on the platform - the single best proxy for developer experience and the strongest predictor of adoption. |
| Time-Boxed Waiver | practice | Exception & Waiver Management | An approved deviation from a standard that carries an owner, a justification, a compensating control and an expiry date after which it is reconsidered. |
| TOGAF | practice | Enterprise Architecture | An enterprise architecture framework whose central element is the ADM, an iterative cycle from vision through business, data, application and technology architecture to implementation governance. |
| TOGAF in Practice | practice | TOGAF | The most widely adopted enterprise architecture framework — useful as a checklist and vocabulary, harmful when followed as a process. |
| Token Audience Validation Audience Restriction, aud Claim | practice | Tokens & JWTs | Verifying that a signed token was issued for the service consuming it, without which a legitimately obtained low-privilege token is replayable against a high-privilege service. |
| Token Budget Enforcement | practice | AI Gateways | Limiting token consumption per user, tenant, feature or time window at a central point, so cost cannot run away unobserved. |
| Token Cost Attribution | practice | AI Cost Management | Assigning inference spend to features, tenants and users, so that cost can be managed by the people who influence it. |
| Tool Schema Design | practice | Tool Calling | Defining the tools available to a model — names, descriptions, parameters and errors — in a way that makes correct selection likely. |
| Trace Sampling Strategy Head Sampling, Tail Sampling | practice | Sampling | Deciding which traces to keep, since retaining all of them at scale is unaffordable and retaining a random few loses exactly the interesting ones. |
| Trade-off Analysis | practice | Meta-Skills | Making the costs of an architectural choice explicit and comparable, rather than presenting a recommendation as if it were free. |
| Trade-off Analysis Methods | practice | Trade-off Analysis Methods | Structured ways to compare architectural options — valuable for making reasoning explicit, dangerous when they produce false precision. |
| Trade-off Framing | practice | Explaining Trade-offs | Presenting a decision as a choice between named costs rather than as a search for a best option, so the audience can exercise the judgement that is properly theirs. |
| Traffic Shadowing Dark Launch, Mirroring, Shadow Traffic | practice | Strangler Fig | Sending real production traffic to a new implementation alongside the old one, serving the old response and comparing - the only reliable way to find undocumented behaviour before it matters. |
| Transactional Audit Emission Audit in the Same Transaction, Complete Audit Guarantee | practice | Auditability | Writing the audit record in the same transaction as the state change it describes, so that a crash cannot produce a change with no record - the property that distinguishes an audit trail from application logging. |
| Trigger Condition Revisit Trigger, Decision Tripwire, Monitorable Assumption | practice | Deciding Under Uncertainty | A specific, observable condition recorded alongside a decision that indicates it should be reconsidered - converting a point-in-time judgement into a monitorable position. |
| Trough-Based Commitment Baseline Reservation, Commit to the Floor | practice | Reserved & Committed Capacity | Sizing reserved capacity to the quietest period rather than the average, because only the trough is capacity you are certain to use for the whole commitment term. |
| Trunk-Based Development TBD | practice | Branching Models | All developers integrate small changes into a single shared branch at least daily, keeping it always releasable. |
| Trunk-Based Development in Practice | practice | Trunk-Based Development | Everyone integrates to one shared branch at least daily, with incomplete work hidden behind flags rather than isolated in branches. |
| Trust Boundary Classification Where mTLS Is Required, Encryption Scope | practice | TLS & Certificates | Writing down which network segments count as trust boundaries, so that mutual TLS is applied where it changes the security posture rather than uniformly or by intuition. |
| Trust Boundary Diagram | practice | Communicating Threat Models | A diagram marking where data crosses between zones of differing trust, which is the structure a threat model is built on and the form security findings are best communicated in. |
| Ubiquitous Language | practice | Domain-Driven Design | A shared vocabulary used identically by domain experts and in the code, so that translation between business and implementation is unnecessary. |
| UI Monorepo Strategy | practice | UI Monorepo Strategy | Whether frontend code lives in one repository or many — a trade between atomic change and independent release. |
| Update Cadence Commitment Next-Update Promise, Incident Comms Rhythm | practice | Presenting to Executives | Promising when the next update will arrive rather than when the problem will be fixed, so the one commitment made during an incident is one the team can actually keep. |
| Usage Telemetry Who Calls This, Consumer Visibility | practice | Platform Telemetry | Per-capability, per-consumer usage data about a platform's own surfaces - the precondition for every deprecation, roadmap and change-impact decision a platform team makes. |
| Usage-Based Access Review Last-Used Entitlement Review, Evidence-Based Access Recertification | practice | Identity & Access Management | Recertifying entitlements against observed use rather than against manager approval, so unused permissions are removed by default instead of being re-approved by someone who cannot evaluate them. |
| Use Case Risk Classification | practice | AI Risk Tiering | Assigning an AI application to a risk tier based on the consequence of it being wrong, which then determines the obligations that apply. |
| USE Method | practice | Observability | For every resource, track Utilisation, Saturation and Errors — the resource-centric complement to request-centric monitoring. |
| User Journey SLO Critical User Journey, CUJ | practice | SLI, SLO & SLA | Defining reliability targets around what a user is trying to accomplish, measured where the user is, rather than around per-request success rates at the server. |
| Utilisation Target | practice | Queueing Theory | The operating point chosen from a latency requirement rather than from cost efficiency, because queueing delay rises non-linearly as utilisation approaches saturation. |
| Utility Tree | practice | Quality Attributes | A structured decomposition of quality attributes into concrete, prioritised scenarios, used to focus architectural analysis on what actually matters. |
| VPC Design | practice | VPC Design | How virtual networks, subnets and connectivity are structured — decisions that are cheap now and extremely expensive to change later. |
| Waiver Expiry Time-Bounded Exception, Expiring Risk Acceptance | practice | Exception & Waiver Management | A mandatory end date on every exception to a standard, so that continuing the exception is an active decision rather than the default. |
| Warehouse Migration | practice | Warehouse Migration | Moving analytics from one platform to another, where the difficulty is almost never the data and almost always the accumulated logic and consumers. |
| Warm Standby | practice | Disaster Recovery | A continuously-replicated, scaled-down running copy of a system in a second location, ready to take traffic within minutes. |
| Waste Elimination Zero-Reliability-Cost Reduction, Cloud Hygiene, Orphan Cleanup | practice | Waste Elimination | Removing spend that buys nothing - orphaned resources, oversized instances, idle environments, over-retention - which is typically a substantial fraction of an unmanaged estate and costs no reliability whatsoever. |
| Waste Elimination | practice | Waste Elimination | Removing spend that produces no value at all — the least controversial and most consistently available saving. |
| Web Performance Budget | practice | Web Performance Budgets | An enforced limit on payload size, resource counts or timing metrics, checked automatically so regressions fail the build rather than accumulating. |
Nothing on this page matches. Search the whole glossary.