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
Configuration Drift Detection practice IaC Modules & Drift Continuously comparing declared infrastructure against what actually exists, so out-of-band change is found on a Tuesday rather than during a rebuild.
Configuration Over Fork Variation as Data, Single Codebase Multi-Market, Parameterised Localisation concept Regulatory Constraints Expressing per-market or per-tenant differences as configuration data and adapters behind stable interfaces rather than as separate codebases, so that improvements ship everywhere and a new market is mostly a …
Configuration Surface Absorbing Variation by Configuration, Yes-Configured pattern Stakeholder Analysis A deliberately designed set of configurable behaviours that absorbs the customisation requests a business will predictably receive, so the answer becomes "yes, configured" rather than "yes, built".
Conflatable Classification Superseding vs Discrete Events, What May Be Dropped practice Device Telemetry at Scale Explicitly classifying each telemetry stream as superseding or discrete, because conflation is the correct overload behaviour for one and silent data loss for the other.
Conflation Last-Value Caching, Superseding Updates pattern Backpressure & Flow Control Discarding superseded updates so that a slow consumer receives the latest state rather than a backlog of stale ones - bounding work by entity count instead of by message rate.
Conflict Copy Conflicted Version, Both-Sides Preservation pattern Sync & Conflict Resolution Preserving both sides of a sync conflict as separate artefacts rather than choosing a winner - the only resolution strategy that never loses user work.
Conformance Automation practice Architecture Compliance Checks Encoding architectural standards as automated checks, so review effort is spent on novel design decisions rather than on verifying known rules.
Conformed Dimension Shared Dimension, Conformed Attribute pattern Dimensional Modelling A dimension defined once and used identically by every fact table, so that measures from different processes can be filtered and grouped together without a reconciliation argument.
Confused Deputy concept Authorization A privileged component tricked into performing an action on behalf of a caller who lacks the authority to perform it directly.
Connascence Connascence of Meaning, Static Connascence concept Cohesion A graded vocabulary for coupling that ranks each dependency by how hard it is to change and how far apart the parties are, so boundaries can be argued with a ranking instead of adjectives.
Connection Draining Deregistration Delay, Graceful Shutdown practice Load Balancing Allowing in-flight requests on an instance to complete before it is removed from service, rather than terminating them at cutover.
Connection Fan-In Ephemeral Client Problem, Serverless Connection Storm concept Network Performance The problem created when many short-lived compute instances each require a connection to a stateful dependency that can only support a small number - and the intermediary pattern that resolves it.
Connection Migration Session Continuity, Seamless Handover concept WebSockets & Realtime Keeping a logical session alive when the underlying network path changes - either in the transport, or reconstructed by the application after a reconnect.
Connection Pinning Sticky Connection Imbalance, L4 Balancing of Multiplexed Protocols concept gRPC APIs The traffic imbalance that appears when a layer-4 balancer distributes long-lived multiplexed connections instead of requests, so new backend capacity receives no traffic until clients reconnect.
Connection Pool concept Performance & Capacity A fixed set of reusable database connections shared by an application's requests, and one of the most common hidden capacity ceilings.
Connection Pool Sizing practice Connection Pooling Choosing how many concurrent connections a service holds to a datastore, where both too many and too few cause outages.
Connection Proxy RDS Proxy, PgBouncer tool Cloud Databases A pooling layer between applications and a managed database that multiplexes many client connections onto a small number of database connections.
Consent Architecture pattern Consent Architecture Capturing, storing and enforcing a person's permissions for specific processing purposes, across every system that acts on their data.
Consent Management practice Privacy Engineering Capturing, storing, honouring and evidencing a data subject's permissions for specific processing purposes, including withdrawal.
Consent Propagation Consent Enforcement, Withdrawal Fanout practice Consent Architecture Carrying a consent decision - and especially a withdrawal - to every system and third party that processes on the basis of it, which is where most consent implementations fail.
Consequence-Based Tiering Proportionate Governance, Risk Tier by Impact practice AI Risk Tiering Assigning governance requirements according to the consequence of a system being wrong and who bears it, rather than by technology - so that the strictest controls apply where they matter and low-risk uses rem…
Consistency Choices practice Strong vs Eventual Consistency Deciding, per operation, the weakest consistency guarantee that is still correct — rather than choosing one model for a system.
Consistency Level Selection practice Strong vs Eventual Consistency Choosing the consistency guarantee per operation rather than per system, matching the cost of coordination to the business consequence of staleness.
Consistent Hashing Ring Hashing concept Partitioning & Sharding A partitioning scheme where adding or removing a node moves only a small fraction of keys, instead of remapping everything.
Consistent Prefix Read concept Consistency Models A guarantee that if a sequence of writes happens in a given order, a reader sees a prefix of that sequence — never an out-of-order subset.
Constrained Protocol MQTT, CoAP, LwM2M protocol Constrained Protocols Messaging protocols designed for devices and networks where power, bandwidth and packet size are hard limits rather than considerations.
Constraint Discovery practice Requirements to Constraints The systematic elicitation of the fixed conditions a solution must satisfy, distinguished from requirements because they are not negotiable and are rarely volunteered.
Constraint Expiry Dated Constraint, Constraint Provenance practice Requirements to Constraints Recording every constraint with its source and its expiry date, so that temporary facts do not get permanently encoded into an architecture.
Constraint Removal Risk Chesterton's Fence, Load-Bearing Friction, Safety-Providing Limit concept Systems Thinking The hazard that a limit, gate or slowness being removed was accidentally preventing something nobody documented - so the improvement's cost lands somewhere unrelated and later.
Constraint Thinking practice Meta-Skills Designing for the budget, timeline, skills, regulations and existing estate that actually exist, rather than for the ones a textbook assumes.
Constraint Thinking practice Constraint Thinking Designing within the real limits — budget, skills, timeline, existing estate, organisational politics — rather than for the abstractly best answer.
Consumer Contract concept Consumer-Driven Contracts A machine-readable record of exactly which parts of a provider's response one consumer relies on, generated from that consumer's own tests.
Consumer Group concept Event Streaming A set of consumers that cooperatively read one stream, with each partition assigned to exactly one member, so the group collectively processes every message once.
Consumer Lag metric Streaming SLOs The gap between the latest offset written to a partition and the offset a consumer group has processed, expressed in records or in time.
Consumer Liveness Gap Zombie Consumer, Progress Blindness concept Competing Consumers The interval in which a queue consumer is alive by every health signal yet is making no progress, so its share of the work stalls while pool-level metrics stay normal.
Consumer-Driven Contract CDC, Pact Testing pattern Consumer-Driven Contracts A machine-checkable expectation written by the consumer of an API and verified against the provider's build, catching integration breaks without a shared environment.
Container Image concept Containers A layered, content-addressed filesystem bundle plus metadata, from which containers are instantiated — immutable by construction and identified by digest.
Container Image Strategy Base Image Policy, Golden Image practice Container Image Strategy The organisational decision about where images come from, what they are built on, and how a base layer fix reaches everything already deployed.
Containers tool Containers Packaging an application with its dependencies into an immutable image, and the orchestration layer that schedules those images across a fleet.
Containment vs Eradication concept Security Incident Response Stopping an attacker's ongoing access versus removing their foothold entirely — sequential phases with different urgency and different risks of doing them wrong.
Content Artefact Release Data-as-Release, Non-Code Release Engineering practice Artifact Management Applying full release engineering - versioning, staged rollout, health gates and a rollback path - to artefacts that are not code but are interpreted by privileged code, such as detection content, rule sets, m…
Content Delivery Network CDN tool Networking A geographically distributed cache that serves content from a location near the user instead of from the origin.
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.
Content Purge Path Takedown Propagation, Cache Purge SLA practice Content Delivery Networks A separate, fast, fail-closed mechanism for removing content from every cache tier, which is what allows long TTLs everywhere else without making removal impossible.
Content Security Policy protocol Frontend Security A response header declaring which sources of script, style and other resources the browser may load, which turns a script injection from a compromise into a blocked request.
Content-Channel Release Path Data Channel Deployment, Ungated Update Path concept Quality Gates Any route by which an artefact reaches a running system without passing the gates that code passes - remote config, feature flags, rules tables, models, CDN rules, detection content - and which therefore carri…
Contention Blind Spot Single-User Environment Blindness, Concurrency Fidelity Gap concept Developer Environments The class of defects a one-user test environment cannot exhibit at all - lock waits, pool exhaustion, races and plan flips - because they require concurrency and production-shaped data rather than correct code.
Context Diagrams practice Context Diagrams The system, its users and everything it talks to — the cheapest, most durable and most under-used architecture artefact.
Context Map practice Bounded Contexts A diagram of the bounded contexts in a system and the relationship type between each pair, making integration expectations and power dynamics explicit.
Context Propagation pattern Correlation IDs Carrying request-scoped identifiers and metadata across every service, thread and asynchronous boundary so a single flow remains traceable end to end.
Context Window concept AI-Era Architecture The maximum number of tokens a model can attend to in one request, holding the system prompt, history, retrieved context, tools and the answer.
Context Window Budget concept LLM Application Architecture The finite token allowance per request, treated as an engineering resource to be allocated deliberately between system instructions, retrieved context, history and output.
Contextual Retrieval Contextual Chunk Prefixing, Contextual Embeddings pattern Chunking & Retrieval Prepending a short generated description of where a chunk sits in its document before embedding it, so that a passage full of pronouns and bare figures still matches the query that should find it.
Continuous Compliance practice Compliance Frameworks Producing compliance evidence automatically and continuously from the systems themselves, rather than reconstructing it before an audit.
Continuous Controls Monitoring CCM practice Continuous Controls Monitoring Automatically testing control effectiveness continuously across the whole population, rather than through periodic manual sampling.
Continuous Integration Discipline practice Continuous Integration Discipline The behavioural commitments that make CI a defect-detection system rather than a build server that runs tests.
Continuous Learning practice Continuous Learning Keeping judgement current in a field where the technologies change constantly and the fundamentals do not.
Continuous Profiling practice Profiling Sampling CPU, memory and lock profiles from production continuously at low overhead, so resource usage can be attributed to specific code paths.
Contract Coverage Gap Contract Blind Spot, Unasserted Field Surface metric Consumer-Driven Contracts The share of a provider's response that a consumer's code reads but its contract never asserts on - the exact surface a provider can delete while every contract check stays green.
Contract Enforcement Point Producer-Side Enforcement, Shift-Left Contract Checking practice Data Contracts Where a data contract is actually checked - which determines whether a breaking change fails in the producer's build or in a consumer's pipeline at 2 a.m.