← @bgSponge

tobi/walgit

Summary

walgit is a single Rust binary that hosts Git in front of S3 or GCS, with no database, no leader, and no local state that matters.

  1. The bucket is the repository.

    Every walgit process is a disposable cache; kill them all and you lose warmth, nothing else.

    Every machine that runs walgit is a disposable cache; the bucket is the repository.

  2. CAS on the manifest is consensus.

    A push uploads an immutable object and becomes visible only when a tiny manifest is rewritten with compare-and-swap; racing instances cannot both win.

    The manifest CAS is the only commit point; everything before it is invisible, everything after it is idempotent and replayable.

  3. Continuity, then small machines.

    The README takes Cursor's WAL-in-object-storage design as-is, then adds a remote reader, a history pack, and bundle-uri so a monorepo can exceed the host.

  4. Reads revalidate first.

    Every read starts with a conditional GET of the manifest; 304 serves the local copy, 200 applies new log entries.

  5. Placement is configured, never inferred.

    Refs-level reads work everywhere; object work only where placement globs assign it.

Read the original ↗Save to your Sponge

Summarized with Sponge. Quotes are the author’s own words.

More from @bg

All readings →