🚀 RepliKube now supports cross-cloud synchronization between AWS and GCP. Read the engineering deep-dive →
Mathematical Precision

The Split-Brain Problem, Resolved at Nanosecond Scale.

Active-Active synchronization requires strict ordering guarantees. RepliKube uses hybrid logical clocks to establish a unified timeline across database engines globally, eliminating transactional conflicts.

What are CRDTs?

Conflict-free Replicated Data Types (CRDTs) are mathematical structures that allow replica clusters to merge data streams autonomously without requiring global database locks. When partitions rejoin, states coalesce into a single correct state based on structural mathematical rules, ensuring data remains correct and accessible throughout outages.

Hybrid Logical Clocks (HLC)

Physical clock systems drift. Standard logical clocks lose scale order under high concurrency. RepliKube pairs physical time ticks with logical counters, generating nanosecond-level timestamps that capture absolute causality across distinct region locations, preventing transaction overwrites.

Flexible Merge Strategies

Configure how RepliKube merges overlapping edits when databases reconnect. We support industry-standard models out of the box, allowing developers to set merge behaviors based on specific database tables or columns.

Latest-Write-Wins (LWW)

RepliKube analyzes logical clock coordinates and promotes the transaction with the latest timestamp, discarding older changes. Ideal for user profile updates or state changes where the most recent event is always correct.

Deterministic Merge

Operations merge mathematically (e.g., counters add up, arrays unionize). Essential for inventory grids, shopping carts, and metrics counters where operations must accumulate.

Flag-to-Human Panel

Conflicting records are isolated in our security quarantine table, prompting alerts to developers to select the correct merger strategy manually when automatic resolution is not desirable.