Area: dedupe — multi-region
The DynamoDB dedupe backend works as-is when each tenant is pinned to a home region (one table per region). Deduplicating globally across regions is possible with DynamoDB multi-region strong consistency (MRSC) global tables, which support the conditional writes dedupe relies on, but MRSC has no TTL. WaveHouse would need a sweeper that deletes lapsed claims and expired retention entries, run as a lease-held singleton.
Trigger: build this when a deployment needs cross-region dedupe. Until then, home-region pinning is the supported model. MRSC also requires exactly three regions and adds synchronous cross-region write latency to every reserve; measure that before adopting it. ScyllaDB (LWT IF NOT EXISTS) is the alternative backend if DynamoDB throughput limits bind first.
Part of #613.
Area: dedupe — multi-region
The DynamoDB dedupe backend works as-is when each tenant is pinned to a home region (one table per region). Deduplicating globally across regions is possible with DynamoDB multi-region strong consistency (MRSC) global tables, which support the conditional writes dedupe relies on, but MRSC has no TTL. WaveHouse would need a sweeper that deletes lapsed claims and expired retention entries, run as a lease-held singleton.
Trigger: build this when a deployment needs cross-region dedupe. Until then, home-region pinning is the supported model. MRSC also requires exactly three regions and adds synchronous cross-region write latency to every reserve; measure that before adopting it. ScyllaDB (LWT
IF NOT EXISTS) is the alternative backend if DynamoDB throughput limits bind first.Part of #613.