concurrency

DE//AGENT currently lists 2 resources under concurrency: 2 tutorials. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Say what ACID transactions on object storage guarantee concurrent writers — via ACID and concurrent writes — why compaction and ingestion collide
• Schedule compaction outside the ingestion window and explain the contention — via ACID and concurrent writes — why compaction and ingestion collide
• Handle a contending OPTIMIZE — compaction is additive, so halt it, no rollback — via ACID and concurrent writes — why compaction and ingestion collide
• Cap max_active_runs and pool limits before a backfill starves the daily run — via Production gotchas — topology, timeouts, concurrency
• Find unsafe retries, missing catchup policy and unbounded concurrency — via Production gotchas — topology, timeouts, concurrency
• Monitor backfill progress, resource contention and validation pass rate — via Production gotchas — topology, timeouts, concurrency

These resources map to stages: Lakehouse (1), Orchestration (1). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. ACID and concurrent writes — why compaction and ingestion collide score 34.15 — intermediate
2. Production gotchas — topology, timeouts, concurrency score 34.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

• ACID and concurrent writes — why compaction and ingestion collide — What ACID on object storage actually guards, and where it stops: Delta commits transactions on files, but compaction is also a writer, and the two meet in the ingestion window. Lea… details
• Production gotchas — topology, timeouts, concurrency — The DAG failures that become pages: unbounded concurrency, missing catchup policy, and a backfill that starves the daily run — cap them with max_active_runs and pools, then wire th… details

Adjacent topics: tutorial (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.