Skip to main content

AI & assistant-friendly summary

This section provides structured content for AI assistants and search engines. You can cite or summarize it when referencing this page.

Summary

Last-write-wins is not a CRDT—it is how Global Tables lose cart merges. When to use counters, OR-Sets, and conflict-free merges vs when to keep a single Aurora writer.

Key Facts

  • June 2026: Multi-Region active-active without a merge strategy is how eventual consistency anti-patterns ship—users see flickering state, not “high availability
  • Anti-patterns 1
  • RWM on same record across Regions without merge → lost updates 2
  • Cache-aside as source of truth across Regions 3
  • On AWS, implement in app layer or use services with documented merge (DynamoDB counters are not full CRDTs)

Entity Definitions

Aurora
Aurora is an AWS service discussed in this article.
DynamoDB
DynamoDB is an AWS service discussed in this article.
SQS
SQS is an AWS service discussed in this article.
ElastiCache
ElastiCache is an AWS service discussed in this article.

CRDTs and Eventual Consistency Anti-Patterns on AWS

Quick summary: Last-write-wins is not a CRDT—it is how Global Tables lose cart merges. When to use counters, OR-Sets, and conflict-free merges vs when to keep a single Aurora writer.

Key Takeaways

  • June 2026: Multi-Region active-active without a merge strategy is how eventual consistency anti-patterns ship—users see flickering state, not “high availability
  • Anti-patterns 1
  • RWM on same record across Regions without merge → lost updates 2
  • Cache-aside as source of truth across Regions 3
  • On AWS, implement in app layer or use services with documented merge (DynamoDB counters are not full CRDTs)
CRDTs and Eventual Consistency Anti-Patterns on AWS
Table of Contents

June 2026: Multi-Region active-active without a merge strategy is how eventual consistency anti-patterns ship—users see flickering state, not “high availability.”

Anti-patterns

  1. RWM on same record across Regions without merge → lost updates
  2. Cache-aside as source of truth across Regions
  3. SQS at-least-once without idempotent handlers (looks like consistency bug)

CRDTs (when they help)

Conflict-free replicated data types (counters, OR-Sets, LWW-Element-Set with care) suit collaboration and device sync. On AWS, implement in app layer or use services with documented merge (DynamoDB counters are not full CRDTs).

Opinionated take: Prefer single-writer Aurora Global for financial aggregates; use CRDT-style merges only when product accepts semantic merge rules in writing.

AWS map

PatternService
Active-active itemsDynamoDB Global Tables + version attribute
Session syncElastiCache + sticky + short TTL
Ordered workflowSQS FIFO + dedup

What to do this week

  1. Document merge function for each Global Table entity.
  2. Add integration test simulating concurrent cross-Region writes.
  3. Metric: conflict resolution count per hour.

What this guide doesn’t cover

Distributed locks—next guide in track.

PP
Palaniappan P

AWS Cloud Architect & AI Expert

AWS-certified cloud architect and AI expert with deep expertise in cloud migrations, cost optimization, and generative AI on AWS.

AWS ArchitectureCloud MigrationGenAI on AWSCost OptimizationDevOps

Recommended Reading

Explore All Articles »