Architecture

Non-Blocking Concurrency Control

A concurrency model for lakehouse table formats that uses distributed timelines rather than locks or optimistic retries, allowing multiple writers to simultaneously mutate the same table and rows without blocking or failing commits. Native to Apache Hudi 1.0.

5 connections 3 resources

Summary

What it is

A concurrency model for lakehouse table formats that uses distributed timelines rather than locks or optimistic retries, allowing multiple writers to simultaneously mutate the same table and rows without blocking or failing commits. Native to Apache Hudi 1.0.

Where it fits

Replaces Optimistic Concurrency Control (OCC) as the write coordination mechanism for high-velocity streaming and CDC workloads on object storage. OCC forces constant retries under concurrent write contention, degrading throughput. NBCC assigns each writer an independent timeline, merging results asynchronously.

Misconceptions / Traps
  • Not the same as eventual consistency — writes are still serializable via timeline ordering and sequence number resolution.
  • Does not eliminate the need for compaction — background merge of timelines is still required for read performance.
  • Currently Hudi-specific; not available in Apache Iceberg or Delta Lake, which remain on OCC.
Key Connections
  • enables Apache Hudi — core concurrency model for Hudi 1.0 architecture
  • enables CDC into Lakehouse — allows high-frequency CDC ingestion without commit conflicts
  • solves Read / Write Amplification — eliminates retry-induced write duplication under contention

Definition

What it is

A concurrency model for lakehouse table formats that uses distributed timelines rather than locks or optimistic retries, allowing multiple writers to simultaneously mutate the same table and rows without blocking or failing commits.

Why it exists

Optimistic Concurrency Control (OCC) forces constant retries under high-velocity concurrent write workloads, degrading throughput and causing commit failures. Non-Blocking Concurrency Control assigns each writer an independent timeline, merging results asynchronously. Native to Apache Hudi 1.0, it enables high-frequency CDC ingestion without the commit contention that cripples OCC-based formats under streaming loads.

Primary use cases

High-velocity CDC ingestion into lakehouse tables, concurrent multi-writer streaming pipelines, real-time lakehouse architectures requiring sub-minute data visibility.

Connections 5

Outbound 5

Resources 3