Active-Active Shared-Nothing Database Architecture | Capital One


Getting the Basics

State of the Application

Traditional Approaches

Brown-Out Period

Hot Standby

CAP Theorem

Eventually Consistent State

Conflict Resolution

Conflict Resolution Handling Techniques

Architectural Decisions

Application Design Patterns

Stateless vs Stateful Applications

Pattern 1: Many Masters but Only One Active

Pattern 2: One Master and Many Standbys (Readers)

Pattern 3: One Feeder and Many Readers

Pattern 4: Many Masters but Updated by Application

Pattern 5: Multiple Masters Buffered Writes


Key Takeaways

Award winning data management and engineering leader, Chief Architect of Cloud Data at JPMorganChase, raspberry pi junkie, dad and husband.