Cursor Uses S3 WAL to Scale Git Storage to More than 300 Pushes per Second
Cursor’s Continuity makes an S3-backed write-ahead log the durable source of truth for Git repositories; local NVMe copies become disposable warm caches. Pushes are acknowledged only after persistence, and replicas verify their state against S3, so lost UDP gossip can delay convergence without making stale reads authoritative.
Cursor reports linear read scaling to 100 replicas and over 300 pushes/s on S3 Express One Zone in synthetic tests; these are vendor-reported results, not independent benchmarks. The design trades synchronous replica coordination for object-store validation, asynchronous replication, and extra bandwidth. InfoQ has no reader-comment section; it cites a practitioner who flagged the performance numbers as unverified.