Cursor's New 'Continuity' System Rewrites Git Storage With S3-Backed Architecture, Hitting 300+ Pushes Per Second

Cursor's new Git storage system, Continuity, is revolutionizing repository hosting by replacing traditional packfile architecture with an S3-backed write-ahead log, achieving over 300 pushes per second and fully consistent reads across 100+ replicas — a major leap beyond GitHub's industry-standard Spokes system.

• Hosting Git repositories at scale is fundamentally difficult due to Git's packfile-based design, which requires random reads across large binary files and makes distributed storage approaches like networked filesystems or object-level distribution prohibitively slow or complex.
• GitHub's Spokes system, the current industry standard, solves this by replicating full Git repositories across multiple servers using three-phase commit for consistency, but struggles with scalability limits as enterprise monorepos and AI-driven workflows demand far more replicas and push throughput than the consensus algorithm can efficiently support.
• Cursor's new Git storage system, Continuity, addresses these limitations by using a write-ahead log stored in S3 as the source of truth, enabling linearizable pushes, fully consistent reads across an arbitrary number of replicas, and simplified operations without external routing databases, achieving over 300 pushes per second on S3 Express One Zone with linear read scaling up to 100 replicas tested.