Skip to main content
Research PaperPeer-reviewed Open Access

Causal Consistency at Global Scale: A Practical Re-evaluation

L. Hoffmann, M. Chen, R. Patel

Journal of Distributed Systems, 2026-07-01

AI Summary

Generated in 2.3s

A 2026 reassessment of causal consistency in geo-replicated systems, with new empirical results from production workloads.

Key Points

  • Causal consistency achievable with sub-50ms overhead in 92% of operations.
  • Protocol refinement reduces metadata size by 64%.
  • 3.1x improvement in tail latency.

Abstract

Causal consistency has long been proposed as a sweet spot between availability and consistency for geo-replicated systems, yet adoption remains limited. We present the first large-scale empirical study of causal consistency in production, analyzing 18 months of operation across three deployments spanning four continents. We identify the specific workload patterns under which causal protocols degrade, and propose two protocol refinements — lazy metadata compaction and speculative dependency resolution — that reduce tail latency by 3.1x without sacrificing safety guarantees. Our refinements have been implemented in two open-source systems and are in production use.

1. Introduction

The CAP theorem establishes that no distributed system can simultaneously provide consistency, availability, and partition tolerance. Causal consistency has been positioned as a practical compromise: it preserves causality (a stronger property than eventual consistency) while remaining available under partitions. Despite a decade of academic interest, production adoption has been sparse.

This paper investigates why. We instrument three production deployments — a social network, a collaborative document editor, and a financial ledger — and collect detailed traces over 18 months.

2. Background

Causal consistency requires that operations related by causality appear in the same order at all replicas, while concurrent operations may appear in different orders. The classical implementation uses vector clocks, which grow linearly with the number of clients and become impractical at scale.

Advertisement

728 × 90

Comments3

You
Sarah Chen
Sarah Chen• 2 days ago

This is exactly what I needed. The breakdown of architectural tradeoffs was particularly illuminating — especially the point about eventual consistency vs. strong consistency being a product decision, not just a technical one.

Marcus Webb
Marcus Webb• 1 day ago

Agreed. Would love a follow-up that goes deeper on the consensus algorithms.

Priya Patel
Priya Patel• 3 days ago

Curious how this approach holds up at 10x the scale. Have you tested with sharded clusters?