← All sources
FOLLOWING / enroute.sh

enroute.sh

1 articles in your libraryVisit blog ↗

Everyone is doing Git on S3 wrong

The article argues that Git-on-object-storage designs using a write-ahead log, like Cursor's Continuity, gain durability and read scaling but remain effectively single-writer and still need full repositories on disk. The author presents Enroute, which instead uses per-repository Raft consensus, stateless compute nodes, optimistic locking, and a segment/layer format confining deltas to commit ancestry, with S3 for durability. Reported peak exceeds 7,600 pushes per second into one repository; reads benchmark near stock Git, but clients pay more to decode served deltas, and garbage collection remains unsolved.