Cache Lease & Singleflight Coalescing
Storage & IndexingAlso known as: Request Coalescing, Thundering Herd Lease
A stampede-prevention mechanism where only one cache-miss worker receives a short-lived lease token to recompute and repopulate a hot key from the database, while concurrent misses wait on the in-flight promise.
CAP Theorem & PACELC
Transactions & ConsistencyAlso known as: Brewer Theorem, PACELC Theorem
Brewer theorem stating that during a network Partition (P), a distributed data store must choose between Linearizable Consistency (C) and 100% Availability (A). PACELC extends this: Even when running normally (E), systems trade off Latency (L) vs Consistency (C).
Causal Consistency
Transactions & ConsistencyAlso known as: Causal+ Consistency
The strongest consistency model achievable while remaining available under network partitions (CAC theorem). Guarantees that all nodes observe causally related operations in the same order, while concurrent operations may be observed in different orders.
Cell-Based Architecture (Pod / Stamp Isolation)
Resilience & OperationsAlso known as: Blast-Radius Deployment Stamp
A blast-radius containment topology that packages a complete, self-contained vertical stack of services, databases, and queues into an independent unit ("Cell") serving a fixed maximum number of tenants, so a catastrophic failure inside one cell affects at most 1-5% of customers.
Ceph Placement Group (PG) & RADOS Peering
Storage & IndexingAlso known as: RADOS Placement Group Peering
The intermediate aggregation layer in Ceph that hashes millions of objects into a fixed number of Placement Groups (PGs) mapped onto OSDs via CRUSH; Peering is the protocol by which OSDs storing a PG agree on the authoritative state of objects after topology changes.
Chandy-Lamport Distributed Snapshot Barriers
Consensus & OrderingAlso known as: Asynchronous Barrier Snapshots
An asynchronous distributed checkpointing algorithm used by Apache Flink that injects lightweight barrier markers into data streams to capture a globally consistent cut of operator states without halting stream ingestion.
Change Data Capture (CDC)
Storage & IndexingAlso known as: CDC Log Tailing, Debezium Pattern
A non-intrusive pattern that tails a database engine commit log (PostgreSQL WAL, MySQL binlog, TiKV Raft log) to stream row-level INSERT, UPDATE, and DELETE mutations downstream in commit order.
Chunked Prefill & Stall-Free Continuous Batching (Sarathi-Serve)
Distributed AIAlso known as: Piggybacked Prefill-Decode Scheduling
An LLM serving scheduling technique that splits long incoming prompt prefills into fixed-size token chunks (e.g., 512 tokens) and piggybacks active decode requests alongside each prefill chunk, eliminating Inter-Token Latency (ITL) generation stalls on mixed-length workloads.
Circuit Breaker
Resilience & OperationsAlso known as: Fail-Fast Circuit
A stability pattern that detects cascading service failures and temporarily fails fast without hitting downstream dependencies. Operates in Closed, Open, and Half-Open states to allow downstream backends time to recover.
Clock Uncertainty Interval & Restart Read Refresh
Transactions & ConsistencyAlso known as: HLC Read Restart Uncertainty Window
In HLC-based distributed SQL databases (CockroachDB, YugabyteDB) without atomic clocks, when a transaction encounters a value written within [T_read, T_read + max_offset], it performs a timestamp bump and checks whether historical reads remain valid to preserve causal ordering.
Cloud FinOps & Cost-per-Transaction Unit Economics
Resilience & OperationsAlso known as: Cross-AZ Egress Optimization
An engineering discipline that attributes cloud compute, storage tiering (NVMe vs S3), and cross-AZ network egress costs directly to business unit metrics (e.g., cost per 1,000 API calls or cost per 1M tokens).
Cloud-Native Vector Database Disaggregation (Milvus)
Distributed AIAlso known as: Milvus Log-as-Data Vector Architecture
A cloud-native vector database architecture that decouples stateless Proxy/Coordinator nodes, streaming log brokers (Pulsar/Kafka) for fresh delta inserts, IndexNodes for heavy asynchronous HNSW/DiskANN builds, and QueryNodes for sealed + growing segment search.
Clustered Index (IOT) vs. Heap Table Secondary Index
Storage & IndexingAlso known as: InnoDB Clustered Primary Key vs PostgreSQL Heap CTID
In a Clustered Index (MySQL InnoDB), B+ Tree leaf pages store the full table row directly ordered by primary key, making secondary index lookups require a double B+ Tree traversal (secondary leaf -> primary key -> clustered leaf) unless covered; in a Heap Table (PostgreSQL), indexes point directly to physical tuple CTIDs.
Coffman's Four Deadlock Conditions
Resilience & OperationsAlso known as: Lock Ordering Deadlock Prevention
The four necessary and sufficient conditions for a resource deadlock: Mutual Exclusion, Hold and Wait, No Preemption, and Circular Wait. Eliminating Circular Wait via strict global lock acquisition ordering guarantees deadlock freedom.
Conflict-Free Replicated Data Type (CRDT)
Consensus & OrderingAlso known as: CmRDT, CvRDT
A distributed data structure (G-Counter, PN-Counter, LWW-Element-Set, OR-Set) whose state-merge function is commutative, associative, and idempotent (join-semilattice), guaranteeing strong eventual consistency without coordination.
Consistent Hashing
Networking & MeshAlso known as: Ring Hashing, Virtual Node Hashing
A distributed partitioning algorithm mapping both nodes and keys to a continuous token ring. Adding or removing a node only redistributes K/N keys on average, avoiding full cluster re-shuffling through virtual nodes (vnodes).
Consistent Hashing with Bounded Loads
Networking & MeshAlso known as: Capacity-Capped Ring Hashing
Mirrokni et al. enhancement to ring hashing (used in Envoy and Vimeo) that caps each node capacity at ceil(c * (total_load / N)) where c = 1.25; if the primary hashed node is at capacity, the request spills clockwise to the next node with available headroom, preventing viral key overload.
Consistent Prefix Reads
Transactions & ConsistencyAlso known as: Snapshot Prefix Ordering
A consistency guarantee ensuring that if a sequence of writes occurs in order W1, W2, W3, any reader observing W2 is guaranteed to also observe W1—preventing causal inversions across multi-shard snapshots.
Control Plane vs. Data Plane Separation & Static Stability
Resilience & OperationsAlso known as: Static Stability Under Control-Plane Failure
The architectural principle that the high-frequency packet/request forwarding path (Data Plane) must continue operating uninterrupted using its last known good local state even if the configuration/coordination brain (Control Plane) suffers a total outage ("Static Stability").
Coordinated Omission in Load Testing
Resilience & OperationsAlso known as: Closed-Loop Benchmark Bias
Gil Tene measurement fallacy where a closed-loop benchmark client waits for a stalled server response before sending the next scheduled request, inadvertently omitting the queuing delay experienced by real open-loop arrivals and underreporting p99 latency by orders of magnitude.
Copy-on-Write (CoW) / Shadow-Paging B-Tree (LMDB / Btrfs)
Storage & IndexingAlso known as: Append-Only Shadow B-Tree
An immutable B-Tree storage variant that never overwrites modified disk pages in place; instead, updates write new shadow pages up to a newly swapped root pointer, providing wait-free MVCC readers and instant crash recovery without a separate redo WAL.
Count-Min Sketch
Storage & IndexingAlso known as: CMS, Heavy-Hitter Sketch
A sub-linear space probabilistic frequency table using d independent hash functions mapping onto a d x w counter matrix. Point frequency queries take the minimum across the d hashed buckets, bounding overestimation error with probability 1 - delta.
Covering Index (Index-Only Scan)
Storage & IndexingAlso known as: Index-Only Scan
A secondary index that includes all columns referenced in a query SELECT, WHERE, and ORDER BY clauses (via INCLUDE payload columns), allowing the database engine to answer the query purely from the B+ Tree leaf pages without random heap/clustered table lookups.
CPU Cache Line False Sharing
Resilience & OperationsAlso known as: 64-Byte Cache Line Ping-Pong
A hardware performance pathology where independent threads on different CPU cores modify distinct variables residing on the same 64-byte L1/L2 cache line, forcing continuous MESI cache-coherency invalidations across the interconnect.
Crash Fault Tolerance (CFT) vs. Byzantine Fault Tolerance (BFT)
Consensus & OrderingAlso known as: 2f+1 Crash vs 3f+1 Byzantine Quorums
CFT protocols (Raft, Paxos) tolerate up to f benign crash/network faults with 2f + 1 nodes; BFT protocols (PBFT, HotStuff) tolerate up to f arbitrary malicious or corrupted nodes sending conflicting signed messages, requiring at least 3f + 1 nodes.
CRUSH (Controlled Replication Under Scalable Hashing)
Storage & IndexingAlso known as: Ceph CRUSH Placement
A pseudo-random, deterministic data placement algorithm used by Ceph that computes object storage OSD targets directly from cluster topology maps and failure-domain rules without a central metadata lookup table.
Cryptographic Merkle Tree & Verifiable Data Integrity
Storage & IndexingAlso known as: Hash Tree Anti-Entropy
A binary or k-ary hash tree where leaf nodes store cryptographic hashes of data blocks and parent nodes store hashes of their concatenated children, allowing two replicas to isolate divergent key sub-ranges in O(log N) network exchanges.
Cuckoo Filter
Storage & IndexingAlso known as: Deletable Probabilistic Filter
A compact probabilistic set-membership data structure based on Cuckoo hashing of compact fingerprints that supports dynamic key deletions with lower space overhead than Bloom filters for false positive rates epsilon < 3%.