Patterns¶
Design patterns: circuit breaker, saga, CQRS, bulkhead, staged rollout, etc.
405 pages
Most-cited¶
- Staged rollout 8 sources — Progressively roll out a change — code, config, feature flag — starting in a
- Specialized agent decomposition 6 sources — Build per-domain agents (storage, databases, client-side traffic,
- Central proxy choke point 5 sources — Central proxy choke point is the organisational-scale
- Tool-surface minimization 5 sources — Tool-surface minimization is the discipline of keeping the number
- Cheap approximator with expensive fallback 4 sources — Serve most queries with a fast, low-cost ML approximator;
- Fast rollback 4 sources — Ability to revert a change to a known-good state quickly — ideally within
- Measurement-driven micro-optimization 4 sources — Pick the code worth optimizing by production profiling, not
- Prototype before production 4 sources — Prototype before production — before committing to an
- Two-stage evaluation 4 sources — Two-stage evaluation is the pattern of splitting a per-event
- Unified billing across providers 4 sources — Unified billing across providers is the cost-management
- AI Gateway provider abstraction 3 sources — AI Gateway provider abstraction is the pattern of routing all
- Caching proxy tier 3 sources — Interpose a stateless proxy tier speaking the cache's native wire
All pages (A–Z)¶
- A/B-Test Rollout with Percentile Guardrails — When shipping a performance-sensitive change whose impact is noisy
- Achievable-target-first migration — For a large multi-team migration, pick a tractable, well-aligned first
- Actionable error messages (as agent-recovery primitive) — Actionable error messages replace generic errors
- Active / Dormant User Training Split — Recommendation systems must serve two populations from the same model:
- Additive capability ladder — Structure an agent's (or any untrusted-code consumer's) execution
- Agent-assisted label validation — Use the same agent you are trying to evaluate to assist with
- Agent training-crawler redirect — Classify AI-training crawlers at edge + redirect them to a
- AI Gateway provider abstraction — AI Gateway provider abstraction is the pattern of routing all
- AI review risk tiering — Classify every incoming change into a small number of risk tiers before any AI reviewer runs, and use the tier to decide how many agents to …
- Alarm aggregation per entity — Once detections pass validation + become alarms, do not forward
- Alert backtesting — Replay a proposed alert expression against historical metric data to
- Alerts as code — Treat each alert as a first-class software artifact: authored with IDE-style
- All-layer ensemble decoding — At the LLM
- Allowlisted read-only agent actions — Constrain an LLM-driven agent's side effects to a static allowlist
- Anonymous attribute proof — Anonymous attribute proof is the design pattern of replacing
- Approver / discarder filter — The approver / discarder filter is a named dual used in Datadog's
- Asset Preload Prediction — In SSR apps the server only learns which JS bundles the page needs
- AST-based query generation — When a user-facing query language must support recursive or
- Async block-clone for stateful migration — Relocate a stateful workload (VM + attached large volume)
- Async middleware inspection — An application-server middleware (e.g., a framework-provided
- Async-projected read model — Async-projected read model is the operational shape of CQRS: a
- Atomic conditional batch claim — When a scheduler needs to pop a variable-size batch bounded by a
- Audit-then-refactor migration — A repeatable playbook for rolling out a new code-level invariant
- Auto-scaling telemetry collector — Run the telemetry-collection tier (metrics / logs / traces scrapers and
- Automate account lifecycle — In an
- Automated configuration mapping — Automated configuration mapping is the migration pattern where
- Automatic provider failover — Automatic provider failover is the pattern of routing an
- Autonomous distributed mitigation — Autonomous distributed mitigation is the architectural posture
- Autotuned execution pipeline selection — When a workload has multiple viable execution pipelines with
- Backup and restore tier — DR tier where nothing runs in the recovery environment during
- Behavior-discrepancy sampling — Behavior-discrepancy sampling is the pattern of prioritising
- Bisect-driven regression hunt — Bisect-driven regression hunt is the canonical debugging pattern for "something got worse after an upgrade, but I don't know what" problems.…
- Blobless clone + lazy hydrate — Blobless clone + lazy hydrate is the concrete pattern for
- Block-level continuous replication — Replicate changes at the block-device layer, continuously
- Blue/green service-mesh migration — Blue/green service-mesh migration is the pattern for cutting
- Bootstrap Then Auto-Follow — When a policy-based automation primitive only applies to
- BPF filter for API event source — Manufacture a control-plane event that a kernel / SDK / library
- Buffered resumable inference stream — Buffered resumable inference stream is the pattern of having
- Build-tag dependency isolation — Keep an unwanted dependency out of some Go binaries by marking
- Build without the bytes (BwoB) — Skip downloading cached action outputs to the client unless a
- Bulk-write + prefetch + parallel — the batch-optimization framework — When batch ETL jobs regress after migrating from an in-engine
- BYO model via container — BYO model via container is the pattern of an inference
- Caching proxy tier — Interpose a stateless proxy tier speaking the cache's native wire
- Canonical entity ID — Canonical entity ID is the pattern of resolving every
- Canonical tag as crawler redirect — Use existing tags as the declarative
- CDP proxy for headless browser — CDP proxy for headless browser is the pattern of standing up a
- Central proxy choke point — Central proxy choke point is the organisational-scale
- Central telemetry aggregation — In a multi-account platform (especially
- Centralized Embedding Platform — Centralized embedding platform is the pattern of operating a
- Centralized forward declarations (Fwd.h per directory) — When a codebase chooses concepts/forward-declaration over #include
- Centralized identity federation — Operate one external identity provider (an IdP — SAML / OIDC /
- cGroup-scoped egress firewall (eBPF) — cGroup-scoped egress firewall (eBPF) is the pattern of
- Change-detection ingestion — Change-detection ingestion is the optimization of comparing a
- Chargeback / Cost Attribution — Pattern: the infrastructure tier that does the expensive thing
- Cheap approximator with expensive fallback — Serve most queries with a fast, low-cost ML approximator;
- Checkpoint-resumable fiber — Run long-running agent work (tens of minutes to days) as a
- CI/CD agent guardrails — Scale AI-agent autonomy progressively over time by layering
- CI regression-budget gate — A CI regression-budget gate is the pattern of (1) identifying a scalar
- Client-side schema validation — Validate events against schemas in a shared client library, on the
- Co-located inference GPU and object storage — Run inference GPUs and the object storage that holds their model
- Code generation over tool calls — Instead of presenting an LLM agent with N individually-described
- Cohort percentage rollout with explicit inclusion criteria — Specialisation of patterns/staged-rollout for fleet-wide
- Cold-to-Hot Vector Tiering — Cold-to-hot vector tiering is the operational pattern of storing
- Colocated child actor RPC — When an agent (or any parent actor) needs to delegate work to
- Colocation Sharding — Group related tables that share a shard key into a colocation ("colo"), and make the colo the unit of physical shardi…
- Comparative documentation benchmark — Benchmark your documentation site's agent-consumption cost
- Comparative RUM benchmarking — You want to publish a credible, network-fair comparison of
- Component-tree simplification — Flatten a component tree composed of many thin reusable wrappers
- Conditional child state scoping — Move expensive / rarely-active state into conditionally-rendered
- Conditional Write (Compare-and-Set on Storage) — A conditional write is a storage-layer primitive that performs a
- Connector transformations + enrichment API — Expose two distinct per-tenant customisation surfaces on a
- Consistency Checkers — SQL-based invariant tests that compare expected system state against data
- Consolidate database and search — Collapse the "primary database + bolt-on search engine + sync
- Constant-time state map — Replace O(n) array scans / multi-hop lookups on a hot path with
- Continued pretraining for domain adaptation — Take a capable open-weights foundation model, continue-pretraining it on a balanced mix of domain-specific and general-domain replay data, w…
- Coordinator / sub-reviewer orchestration — Decompose an AI-driven review / critique / analysis task into:
- Credentialed proxy sandbox — When an agentic system needs to execute model-generated code that
- Cross-Cloud Replica Cache — Pattern: the canonical copy of a dataset lives in one cloud; a
- Cross-index unified retrieval — Let a caller query across many physically-separate search indexes in a single call, with the platform owning the fan-out, merge, and rank — …
- Cross-model prompt adaptation — Cross-model prompt adaptation is the pattern of treating the
- Cross-partition failover — An architecture that deploys duplicate infrastructure across two or
- Crossplane composition (XRDs + Compositions) — Package N cloud primitives behind one high-level Kubernetes custom
- CTE-emulated upsert — CTE-emulated upsert is a Postgres query pattern for "insert-or-update" semantics
- Custom benchmarking harness — When a vendor-supplied benchmark tool doesn't match your workload
- Custom data structure for hot path — When stdlib or well-known crate data structures don't match
- Customer-Driven Feature Prioritization — A product-development practice: feature selection and ordering are
- Dark-ship for behaviour parity — Dark-shipping is running a new implementation of a subsystem
- Data Application Productization — When a question or workflow repeats often enough, turning the underlying
- Data-driven allowlist via monitoring mode — Shipping a default-deny enforcement system (allowlist-based access
- Data-driven annotation curation — Replace blanket per-site daily annotation with intelligent,
- Data-placement spreading — For each new object, choose a different subset of drives to place it on — even for objects owned by the same tenant, in the same bucket. The…
- Debezium + Kafka Connect CDC pipeline — The canonical open-source shape for [[concepts/change-data-capture|
- Default-on security upgrade at no additional cost — A product-strategy pattern where an infrastructure provider ships
- Deny-overrides-allow — An effect-resolution rule in permissions engines where, given a
- Deterministic intent with ML fallback — For command-interpretation surfaces (voice assistants, chat bots,
- Deterministic rule ordering — Deterministic rule ordering is the pattern for building a ranker /
- Developer portal as interface — An internal developer platform exposes its capabilities through
- Device blocklist from telemetry — A device blocklist from telemetry rolls out a new
- Disable legacy crypto before rotate — After enabling new cryptographic primitives (typically post-
- Disaggregated inference stages — Disaggregated inference stages is the serving-side architectural pattern of splitting distinct stages of a multi-stage inference pipeline on…
- Disposable VM for agentic loop — Instead of running an LLM-driven
- Disruption-Budget-Guarded Upgrades — Disruption-budget-guarded upgrades is the pattern of protecting
- DNS proxy for hostname filtering (eBPF) — DNS proxy for hostname filtering (eBPF) is the pattern of
- Durable-Object-backed Git server — Durable-Object-backed Git server is the substrate pattern for
- Draft-verify inference — Draft-verify inference is the generalised pattern behind
- Dual-system sync during migration — Dual-system sync during migration is the intermediate-state
- Dual-write migration — Dual-write migration is a pattern for protocol/backend transitions
- Dual-Write to Online and Offline Store — Dual-write to online and offline store is the ingestion-time
- Durability review — A durability review is a structured gate applied to any code change that could affect a service's durability posture. The artifact is modele…
- Dynamic allowlist for safe exposure — Maintain a runtime-configurable allowlist of
- Dynamic control loop tuning — Replace a static, manually-tuned threshold (or weight, or budget)
- Dynamic /index.md fallback — Expose every page's markdown representation at
- Dynamic-schema field-name encoding — Reduce document size + storage footprint of MongoDB collections
- Dynamic UI generation — Instead of returning text-only responses, an agentic interface
- Earliest-finish-job greedy — Earliest-finish-job greedy is the online scheduling
- Edge-managed protocol complexity — Edge-managed protocol complexity is the pattern in which
- Edit-quiescence indexing — Edit-quiescence indexing is the indexing-trigger pattern of
- EKS add-on as lifecycle packaging — An AWS-native Kubernetes operator (or dependency controller) ships
- EKS Cost Allocation Tags — Use AWS Billing's split cost allocation data for EKS to map
- Embedded routing header as address — Use a large address space (typically IPv6, 128 bits) to
- Embedding Ingestion Modes (batch + Insert API + on-the-fly) — Embedding ingestion modes is the pattern of a centralized
- Emergency bypass — An explicit, audited escape hatch around the normal change-management pipeline
- End-to-end recompute — End-to-end recompute is a pipeline-design pattern where the
- Envelope-and-verify — For high-stakes agentic AI systems, the architecture Byron Cook prescribes is a three-part discipline:
- Ephemeral preview environments — Deploy a full application stack (or a scoped subset) as a
- Event-driven config refresh — A reactive cache-invalidation pipeline for configuration data that
- Executable specification — Write a compact model of the system under test, in the same language as the production implementation, commit it to the same repo, and conti…
- Explainability log — Explainability log is the pattern of emitting a structured,
- Explicit backpressure policy — When a bounded buffer in a streaming pipeline fills and the
- Explicit Boundary Translation — Explicit boundary translation is the implementation pattern that
- Explicit placement hint — Pin a serverless / edge compute unit to a specific region
- Expression-def triples DSL — A boolean-logic DSL built from a single primitive —
- eXtreme Modelling — eXtreme Modelling (XM) is the methodology proposed by Methni, Madeira,
- Fan-out StackSet deployment — A single CI/CD pipeline in a central administrator account triggers
- Fast rollback — Ability to revert a change to a known-good state quickly — ideally within
- Feature-gate pre-migration network rewrite — When migrating workloads would break users who have hardcoded
- Feature-Phone Frontend (Thin-edge Sophisticated-backend) — Feature-phone frontend is the architectural shape used by
- Fewer, larger shards for latency-sensitive workloads — In a coordinator-fan-out search system (OpenSearch / Elasticsearch /
- Field-level sensitivity tagging — Attach a sensitivity category to every database column in a
- Five-phase managed-service migration playbook — Move a large self-managed production deployment (database, search
- Flip lookup direction — When a hot-path operation is expressed as "for each element in
- Forecast → Estimate → Plan (three-component capacity planner) — Decompose predictive-capacity-planning into three independent
- Formal Methods Before Shipping — New protocol — replication, failover, reconfiguration, a
- Framework-managed executor pool — Give a block of code to a framework; the framework manages a pool
- FSM RPC for config metadata transfer — When a cross-host operation (migration, replication, failover)
- Full-stack IO instrumentation — Instrument every IO at multiple points in every subsystem of the storage stack — plus run continuous canary workloads — so that (a) the true…
- Fused decompress + tensor-core matmul — When weight compression buys memory-bandwidth headroom on a
- Game-engine stack for web canvas — A three-language client+server split for browser applications whose
- Git-based config workflow — Treat runtime configuration — feature flags, limits, tunables, ACLs — as
- Git protocol as API — Git protocol as API is the pattern of exposing a service over
- Golden path with escapes — Golden path with escapes is the platform-team design where the
- Gossip fingerprint propagation — Gossip fingerprint propagation is the pattern of sharing
- Gradual API-surface rollout — When a rewrite affects behaviour that is consumed through multiple
- Gradual transpiler-driven language migration — Migrate an entire codebase from source language A to target language
- Graphics API interface layer — A graphics API interface layer is an internal abstraction that
- Groundtruth upper-bound benchmark — When a multi-stage pipeline's end-to-end quality is mediocre, a
- Grouped linear quantization — Share a scale (and optionally a zero-point) across a
- Hackathon to platform — Start an internal platform from a short, time-boxed hackathon
- Hardware-native quantization — Push quantization metadata (scales, zero-points, block-scale
- Heterogeneous cluster provisioning — Heterogeneous cluster provisioning is the EC2-capacity pattern of
- Hidden agent directive in HTML — Embed a short, human-invisible, LLM-visible imperative in
- Hierarchical Multi-Task Geo Prediction — Hierarchical multi-task geo prediction is a pattern for injecting
- Hot-swap retrofit (fleet upgrade in flight) — Upgrade the live production fleet in place, one server at a time, without customer-visible disruption — even when the upgrade involves physi…
- Human-calibrated LLM labeling — Human-calibrated LLM labeling is the pattern of training a
- Hybrid batch + streaming + direct-write ingestion — Hybrid batch + streaming + direct-write ingestion is the
- Hybrid cloud testing — For cloud services that cannot be fully emulated locally, keep
- Hybrid lexical+vector interleaving (min-max normalized, exact-match boosted) — Hybrid lexical+vector interleaving is a specific score-fusion
- Identity-to-key binding — When a token attests both a user's identity and a
- Inbound-classify-persist-reply pipeline — An email agent has to do the same five things on every inbound
- Incremental AI re-review — When an AI code-review agent runs again on a merge request that already has prior findings, don't treat the new run as a blank slate. Feed t…
- Independent scaling tiers — A single-tier system has one scaling lever — add more servers.
- Init as credential broker — Make the init binary of a VM / micro-VM / container detect
- Initiator / responder role inversion — Cut the connect-setup latency of a symmetric point-to-point
- Instance-shape right-sizing for CI workers — Pick the EC2 (or equivalent) instance type by workload shape
- Instruction library prompt composition — Instruction-library prompt composition is the constrained /
- Intent-preserving query translation — When migrating queries (observability dashboards, alert expressions, SQL,
- Interleaved ranking evaluation — Evaluate a candidate ranking change faster and more sensitively
- Interrupt and restart — Interrupt-and-restart is a preemption policy for
- Invariant-driven programming — Invariant-driven programming is the discipline of, for every
- Issuer / attester / client / origin roles — The RFC 9576 four-role decomposition is the architectural
- JIT provisioning on first packet — Install per-peer state in a kernel / data-plane primitive
- JSONL streaming child process — Embed an AI coding agent (or any long-running LLM tool) as a child process driven by three choices:
- Judge query-context tooling — Judge query-context tooling is the pattern of giving an
- JWT tenant-claim extraction — Never accept tenantId from the request. Always extract it from
- KV-aware routing — KV-aware routing is the load-balancing pattern for LLM serving in which the router's target-selection decision is driven by which replica ho…
- Lambda authorizer — A Lambda authorizer is a Lambda function
- Language rewrite for concurrency — Language rewrite for concurrency is the architectural pattern of
- Launch-Minimal Runtime — Launch-minimal runtime is the pattern of shipping a platform or
- Layered testing strategy — Compose a tiered test suite where each layer tests a different
- Lazy pull pipeline — Compose streaming pipeline stages so that no stage executes
- Learned distribution over point prediction — When downstream decisions are cost-asymmetric in the
- Lifetime-aware rescheduling — After initial placement, continue tracking the workload's
- Lightweight aggregator in front of broker — When the application's required batching semantics are not
- Load-test at scale (before real workloads) — Load-test at scale is the practice of running a synthetic
- Local-emulation-first — Prefer a local emulator over a cloud deployment as the default
- Local mirror of remote API — Serve the same API shape locally that your cloud serves
- Loopback isolation (find the real bottleneck) — Determine which layer in a stack of queues/drivers is the real bottleneck (or a source of cross-tenant interference) by replacing each layer…
- Machine-to-machine authorization — Reuse the same fine-grained-authorization architecture built for
- Managed replication platform — Instead of each team hand-assembling point-to-point pipelines
- Managed sidecar — Managed sidecar is the pattern where the vendor owns the
- Measurement-driven micro-optimization — Pick the code worth optimizing by production profiling, not
- Merchant-of-Record Aggregation — Merchant-of-Record Aggregation is the design pattern where a
- Prefer MERGE INTO over INSERT OVERWRITE (Iceberg row-level updates) — On systems/apache-iceberg (and other open table formats that
- Metadata boost at query time — Let query-time business logic (recency, priority, region, tenant tier, language) re-rank already-relevant results, without re-indexing, re-e…
- Metadata-DB + object-cache tier — Architect a globally distributed object store as three
- Middleware Worker adapter — Middleware Worker adapter is the pattern of placing a thin
- Minimize VM Permissions — Treat the sandbox VM's own capabilities — its network reach, its
- Mirror-first repack validation — Mirror-first repack validation is the pre-production step for a
- Modular disaggregated constellation — Modular disaggregated constellation is an architectural-shape pattern for
- Mountable persistent storage — Mountable persistent storage is the pattern of presenting a
- Multi-account AWS isolation — Use separate AWS accounts as the primary isolation boundary to
- Multi-cluster active-active redundancy — Multi-cluster active-active redundancy is the deployment shape of
- Multi-strategy compaction — Instead of a single compaction heuristic, run N strategies concurrently
- Multilayered alarm validation — Turn noisy per-frame detections into auditable alarms by composing
- Multimodal content understanding — Multimodal content understanding is the ingestion-time pattern
- Native Hybrid Search Function — Expose hybrid retrieval — combined lexical + vector search with fusion — as a single first-class …
- No-downtime cluster upgrade — No-downtime cluster upgrade is the deployment discipline of
- Noisy simulated evaluation environment — When replaying an evaluation label
- Nonce-indirection bulk eviction — An invalidation-based cache
- Non-disruptive migration (live tenant relocation) — Move a live tenant's state between servers, hardware generations, or on-disk formats without customer-visible disruption — so the fleet unde…
- Notebook-driven elastic compute — A notebook cell is the unit of work; the cluster is elastic
- Observer-vs-actor animation — In real-time collaboration, render the same edit twice against
- OIDC role assumption for cross-cloud auth — A workload running in platform A (Fly.io, GitHub Actions, a
- Open governance as technical constraint — For an open-source platform whose value proposition depends on
- Open issuer ecosystem — Open issuer ecosystem is the governance pattern required to
- Package Rule auto-generation — When a security tool's allowlist depends on content hashes
- Partial-restart fault recovery — On a failure in a distributed job, restart only the affected
- Partner managed service as native binding — Integrate a third-party managed service (database, vector
- PDU doubling for power headroom — When per-rack power draw exceeds the rack's nominal power budget but
- Peer debugging (scaling the senior engineer) — When a single senior engineer becomes a bottleneck on every hard problem in an org, move to a format where their systems knowledge is pooled…
- Per-Boot Ephemeral Key — Per-boot ephemeral key is the pattern of generating a unique
- Per-instance embedded database — Colocate a single, embedded database (typically SQLite) with
- Per-service config aggregator — Per-service config aggregator: when a central infrastructure service is configured by many tenant teams, shard the configuration into one fi…
- Per-tenant policy store — In a multi-tenant SaaS using
- Performance comparison with scientist — Run old (control) and new (candidate) implementations of a
- Phased CDN rollout — passthrough → managed → auto — Phased CDN rollout: passthrough → managed → auto is the
- Phased migration with soak times — Phased migration with soak times is the migration pattern where
- Pilot-component language migration — When considering switching a significant codebase to a new systems language (a "one-way door" decision), do not start with the hardest or mo…
- Pilot light deployment — DR deployment tier where the data tier in the secondary environment
- Pipe-syntax query language — Pipe-syntax query language is a query-language surface shape where
- Pipeline stage as discrete job — Pipeline stage as discrete job is the pattern of decomposing a
- Pipeline step consolidation — When "more steps" becomes a tax instead of a speedup, group
- Planner / Coder / Verifier / Router loop — Build an agent that solves open-ended problems by planning, executing,
- Platform engineering investment — To make architectures that demand large amounts of structural
- Platform security at the application layer — Apply infrastructure-security techniques — continuous monitoring,
- Pluggable component architecture — Pluggable component architecture takes microservices-style
- Policy gate on provisioning — Gate every infrastructure-provisioning request at admission time
- Policy proof-of-concept branch — When rebuilding an authorization engine — or any system whose
- Policy static analysis in CI — A CI-time linter that walks every authorization policy and rejects
- PoP densification — A global edge / CDN / DNS / DDoS network wins on latency
- Post-inference verification — 1. An AI component (LLM, agent, generator) produces an output y for input x.
- Postgres extension over fork — When building a database product on top of Postgres — even one that replaces core subsystems (replication, concurrency control, durability, …
- Power of Two Choices (P2C) — Power of Two Choices (P2C): instead of picking one backend uniformly at random, pick two at random and route the request to the one with few…
- PR/FAQ Writing (Amazon Working-Backwards Doc) — PR/FAQ is Amazon's internal practice of authoring a new product or
- Pre-disclosure patch rollout — Sequence the security-remediation timeline so the patch is
- Pre-inspection / post-inspection route tables (TGW) — Pre-inspection / post-inspection route tables is the routing
- Pre-token-generation hook — A pre-token-generation hook is a function an identity provider
- Precomputed relevance graph — Precomputed relevance graph is the pattern of building a
- Preload-on-request hint (warm the backend before the client connects) — Preload-on-request hint is a pattern that attacks latency on a
- Presentation Layer Over Storage — Presentation-layer-over-storage treats an application-facing data
- Previous version as dictionary — Previous version as dictionary is the specific compression
- Price Header Negotiation (reactive + preemptive) — Price Header Negotiation is the HTTP-level design pattern for
- Primitive mapping — Kubernetes API to cloud primitives — Pattern. When building a managed Kubernetes offering on top of an
- Product feedback to eval labels — Embed evaluation-label creation in the product surface itself.
- Progressive configuration rollout — Progressive configuration rollout is the same staged-deployment
- Progressive data loading — An evaluation optimization for systems that combine (a) a declarative
- Prompt optimizer flywheel — Prompt optimizer flywheel is the pattern of closing a feedback
- Property-Based Testing — Property-based testing is a testing pattern where, instead of
- Protocol algorithm negotiation — Protocol algorithm negotiation is the protocol-design pattern
- Protocol-compatible drop-in proxy — Build the proxy tier so it speaks the native wire protocol of the
- Prototype before production — Prototype before production — before committing to an
- Proxyless service mesh — Proxyless service mesh delivers service-mesh capabilities — service discovery, L7 load balancing, health-aware routing, mTLS, observability …
- Pull-on-demand replacing push — Replace a push-from-control-plane-to-data-plane provisioning
- Query gateway — Query gateway is the architectural pattern of placing a proxy /
- Query language as agent tool — Query language as agent tool exposes a declarative query
- Rapid fleet-patching via managed service — When a security vulnerability ships in software the vendor also
- Redundancy for heat — Treat replicas and erasure-coded shards as I/O-steering degrees of freedom, not only as durability mechanisms. Every read request has multip…
- Refactor-for-seccomp-filter — When a program needs dynamic access to a sensitive syscall
- Reference-based copy optimization — Reference-based copy optimization is a compaction/merge-side
- Reference hardware for software ecosystem — When your software platform has a hardware dependency whose
- Remote config model routing — Decouple the model-routing decision from the code running the AI workload so operators can flip a switch at the control plane and have every…
- Repo health monitoring — Repo health monitoring = standing up continuous measurement of a
- Response sampling for authorization detection — Sample a configurable fraction of outbound API responses. Extract
- Response status as content policy — Use the HTTP response status-code surface as the protocol for
- Reusable subscriber constructs — Package subscriber-side infrastructure for an event-driven system as a
- Risk-based sequencing — Risk-based sequencing is the migration-ordering pattern where
- Rollback-capable migration tool — A rollback-capable migration tool is a bespoke automation tool
- Rollout escape hatch — A time-bound, individual-scope safety valve that users flip
- Routing rules as config — Routing rules as config is the pattern of expressing
- RUM-validated dictionary selection — RUM-validated dictionary selection is the pattern in which
- Runtime backend swap on failure — A runtime backend swap on failure pattern treats mid-session
- Runtime orchestration toward unidirectional flow — A client runtime that has grown by accretion — layout engines, variable
- Runtime-provisioned per-tenant search index — Make a dedicated search index per tenant (agent, customer, session, language, region, …) a runtime-cheap primitive — created on first appear…
- Runtime Vulnerability Prioritization — Runtime vulnerability prioritization is the pattern of augmenting
- Safe midpoint computation — When computing the midpoint of two indices low and high (both
- Schema-driven interface generation — Generate every interface surface a product exposes — CLI,
- Schema iteration via load testing — Treat schema design as an empirical optimization problem — each
- Schema Registry backward-compat — Integrate a Kafka Schema Registry
- Schema validation before deploy — Analyse database migration SQL before it's applied to the
- Scoped migration with fast-follows — Scoped migration with fast-follows is the pattern of deliberately
- Score-driven standard adoption — Publish a Lighthouse-style per-site scorecard for an emerging
- Seccomp-bpf container composition — Compose the independent Linux isolation primitives —
- Secure tunnel to managed compute — Give a developer's local workstation an interactive / port-forward
- Seed-Recorded Failure Reproducibility — Seed-recorded failure reproducibility is the developer-experience
- Selective indexing heuristics — Selective indexing heuristics is the pattern of applying
- Self-service block approval — When a default-deny enforcement layer (binary authorization, egress
- Separate vs Combined Index (hybrid search topology) — The core architectural choice when deploying hybrid retrieval (lexical + vector): do you keep key…
- Sequential node cordoning — Sequential node cordoning is the node-replacement pattern where
- Server-hydrate visible only — On a server-side-rendered page, hydrate only the portion of the
- Server-side Git repack — Server-side Git repack is the pattern of permanently fixing a
- Serverless driver-worker pattern — Decouple image / event processing into a driver that orchestrates
- Session-affinity header — Session-affinity header is the LLM-serving pattern of asking clients to carry a per-session opaque token as an HTTP header on every turn, us…
- Shader source translator pipeline — A shader source translator pipeline maintains shader source in
- Shadow application readiness — Use live production traffic as the test oracle to pick the supported subset of an API surface, before committing application code to it. Run…
- Shadow migration (dual-run reconciliation) — Shadow migration (a.k.a. dual-run with reconciliation) is the
- Shadow validation of a derived dependency graph — Shadow validation of a derived dependency graph is the pattern
- Shaping vs building — Separate the shaping phase — cheap exploration of possible
- Shard replication for hot keys — Shard replication for hot keys is the auto-sharder pattern for concepts/hot-key relief: when a single key (or small set of keys) attract…
- Sharded views over unsharded DB — Use database views to represent logical shards against a still-unsharded physical database, so horizontally-sharded read/write semantics can…
- Shared kernel resource coordination — Shared kernel resource coordination is the pattern of treating
- Shared state store as topology unifier — Attach a single Kafka Streams state store
- Short-term + long-term forecaster (two-forecaster architecture) — Deploy two forecasters on the same metric at different
- Side-by-side runtime validation — Side-by-side runtime validation is the rollout-risk discipline for
- Sidecar agent — Run a small helper process in the same pod / network namespace as the main
- Signed Bot Request (Ed25519 + JWK directory + RFC 9421) — Signed Bot Request is the design pattern for giving an automated
- Signed commit as device attestation — Use the device-trust X.509 certificate already installed on corporate
- Signed reply-routing header — When an agent sends an email and expects a reply, the inbound side
- Sigstore bundle attestation — Sigstore bundle attestation is the pattern of shipping a signed
- Single-bus multi-account — Split ownership of an event-driven system along two orthogonal axes:
- Single-function forced package split — When a single function in an otherwise-shared package drags
- Single-Node Cluster per App Replica — Deploy one single-node storage cluster on each application
- Single-source service definition — Single-source service definition defines a service's entire
- Single-Threaded Control + Offload Pools — Single-threaded control + offload pools is a concurrency pattern
- Single top-level event handler — Replace N per-component event handlers with one top-level handler
- Skip the intermediate representation — When a multi-stage pipeline stages its data through a format that is
- Slow-start ramp-up (new-pod warmup) — Slow-start ramp-up: when a newly registered backend appears in the load-balancer's pool, cap its share of traffic at a low fraction and ramp…
- SM partitioning (producer / consumer thread groups) — Inside a single GPU kernel, split thread groups into dedicated
- Snapshot-based warm-up (EBS snapshots for CI agents) — Preload CI agent caches into an EBS snapshot. New agents boot
- Snapshot-replay agent evaluation — Capture snapshots of production-state inputs (queries, tool
- _source field slimming with external re-fetch on update — source field slimming with external re-fetch is the
- Specialized agent decomposition — Build per-domain agents (storage, databases, client-side traffic,
- Specialized reviewer agents — Instead of one LLM reviewing every axis of a code change, run N domain-specific sub-reviewers, each with a narrow prompt, narrow tool surfac…
- Split llms.txt per subdirectory — For a large documentation site (thousands of pages), publish
- SSH certificate extension smuggling — Use an existing protocol's extension field to carry
- SSO with ephemeral SSH keys — Replace long-lived SSH keys (the ~/.ssh/idrsa file that
- Staged rollout — Progressively roll out a change — code, config, feature flag — starting in a
- Stager downloads agent for remote control — A small shell snippet (the stager), sent over an
- Starlark configuration DSL — Use Starlark (Bazel's
- State-eviction cron — Keep the hot-set of kernel / data-plane state bounded by
- State transfer on reshard — State transfer on reshard preserves per-key in-memory state when an auto-sharder reassigns a slice from one pod to another. Instead of the s…
- Stateless invalidator — An invalidation-based cache fed
- Static allowlist for critical rules — When an enforcement tool pulls its ruleset from a central sync
- Static pipeline generation — Generate the CI pipeline YAML ahead of time — not at
- Streaming k-way merge (compaction) — A compaction pattern for concepts/lsm-compaction over
- Streaming re-encoding reclamation — Use an existing on-the-fly encoder (typically an erasure-coder)
- Sub-addressed agent instance — A single agent class on a single domain needs to host many distinct
- Sub-field scoping for role trust — Structure your OIDC IdP's sub claim as a hierarchy of
- Subscriber switchover (per-consumer migration cutover) — Subscriber switchover is the cutover pattern where consumers of a
- Supplier co-development — Enter into a long-horizon engineering partnership with a
- Suspense Boundary (progressive rendering) — A Suspense boundary is a declarative "this subtree may not be ready
- Synthetic data generation — Use a controllable generative model (diffusion / image-to-image /
- T-test over bootstrap for production significance testing — Replace the general-purpose but computationally expensive
- Tagged storage routing — Tagged storage routing dispatches each request for a named piece of
- Teacher-Student Model Compression — Teacher-student model compression is the engineering pattern
- Telemetry to Lakehouse — Telemetry to Lakehouse is the pattern of landing operational
- Telemetry-to-RAG pipeline — Build a streaming pipeline that continuously ingests operational
- Temporary SAN for fleet drain — Turn a draining worker's locally-attached storage into a
- Test-case generation from spec — Given a formal specification (typically in TLA+ or a model-checkable
- Tests as executable specifications — Treat the test suite not just as a regression net, but as the
- Third-party dependency quantum assessment — When planning a post-quantum migration, scope assessment must
- Token-budget pagination — Token-budget pagination cuts a tool's response after a fixed
- Token-limit-aware feature prioritization — When the input fed to a language model can exceed the
- Tool-decoupled agent framework — Define agent tools as ordinary code functions + signatures + a short
- Tool-surface minimization — Tool-surface minimization is the discipline of keeping the number
- Trace-checking — Trace-check a production implementation against a formal
- Tree-structured conversation memory — Persist an agent's conversation history not as a flat list of
- Trimmed-automaton predicate filter — A per-file (or per-row-group) approximate set-membership filter
- Trip Classification — Trip classification is the pattern of running each trip (or
- Two-stage evaluation — Two-stage evaluation is the pattern of splitting a per-event
- Two-stage pre-training — contrastive then masked — Train a visual foundation-model encoder in two sequential stages
- TypeScript as code-gen source of truth — Use TypeScript types as the primary source of truth for
- Unified billing across providers — Unified billing across providers is the cost-management
- Unified inference binding — A unified inference binding is an SDK / runtime-binding
- Unified retrieval tool — Unified retrieval tool is the pattern of replacing N
- Unified typespace consolidation — When two (or more) subsystems independently define parallel type
- Uniform buffer batching — A uniform buffer batching pattern amortizes GPU-memory allocation
- Upload-then-poll indexing — Collapse the write → indexed → searchable latency path into a single awaitable API call that returns once the document is fully indexed and …
- Upstream the fix — When a performance / correctness / security issue lives in a
- Virtual Kubelet provider — Pattern. Implement a cloud's managed-Kubernetes offering by
- Visual eval-grading canvas — Visual eval-grading canvas is the pattern of building the
- Warehouse-unload bridge — Warehouse-unload bridge is the pattern for moving OLAP-computed
- Warm standby deployment — DR deployment tier where the secondary environment runs the full
- Webhook-triggered verifier Lambda — On every event of interest at a SaaS (a Git push, a PR update, a build
- Weekly Operational Review — Reliability compounds only if failures are learned from across
- Weight-only vs activation quantization — When deploying quantized attention
- Weighted DNS traffic shifting — Weighted DNS traffic shifting uses DNS records with integer
- Weighted-sum strategy migration — Weighted-sum strategy migration: when gradually migrating between two algorithms that produce the same shape of numeric output (e.g. two loa…
- Well-known endpoint discovery — Publish a protocol-known metadata resource at a fixed
- Workflow-orchestrated pipeline provisioning — When a platform needs to provision multi-step data-plane
- Workload-segregated clusters — Workload-segregated clusters is the operational pattern of
- Wrapper-script arg injection — A caller tool with a pluggable-program interface invokes your
- Zero injection for sparse counters — A transparent fix for Prometheus' silent undercounting of sparse
- Zero-trust re-verification — Zero-trust re-verification re-runs the authorization check at
- ZKP capability disclosure — Prove possession of a dangerous capability using a
- Zone-affinity routing (with spillover) — Zone-affinity routing prefers in-zone / in-region backends over cross-zone ones for latency and cost. With spillover (the version that actua…