What do you do when a customer needs 1,000 Git repos created per second, and you have three weeks to deliver? You build your own Git server on Durable Objects. Dillon Mulroy breaks down how a small but mighty team of three shipped Cloudflare Artifacts as a closed beta,... on time.show more

@dillon_mulroy who is starting 1,000 side projects a second

@dillon_mulroy For lovable ?

@dillon_mulroy three people shipping 1000 git repos per second in three weeks is actually insane. i would’ve guessed six months minimum for that scale.

@dillon_mulroy legends

@dillon_mulroy One Durable Object per repo I'd guess? Curious how big a repo gets before that starts to hurt.

@dillon_mulroy can you point a plain git clone at it, or do the repos only go through the artifacts api?

@dillon_mulroy if one repo outgrows a single Durable Object's storage, do the packfiles get split across objects?

@dillon_mulroy You use @pierrecomputer

just curious, does it use native structures and indexes for objects, trees, refs, etc, or is sqlite mostly used as a KV/blob store? I ended up building a git compatible engine (client + server) directly on sqlite, with git state modeled in relational tables it lives in the same DO as the agent, so the virtual fs and git commands can benefit from optimized sql instead of going through filesystem abstractions

@dillon_mulroy Who won the GitHub contest? I wasn’t able to finish mine in time

@dillon_mulroy three weeks sounds like a nightmare for that scale