Nathan VanBenschoten
@natevanben
Followers
389
Following
305
Media
2
Statuses
88
Distributed Systems @turbopuffer, previously @CockroachDB
New York, NY
Joined April 2013
Compare-and-swap has an infinite consensus number. It’s universal – powerful enough to solve any consensus problem. That’s why I’m excited about what we built here. It’s compare-and-swap all the way down.
S3’s conditional writes were the key ingredient that made our architecture possible. now it's our time to pay it forward
0
0
12
RT @Sirupsen: we are looking for a p99 engineer to work on infra/autoscaling/k8s tooling for the 10s of clusters (soon 100s) we run across….
0
17
0
RT @turbopuffer: modern NVMe drives are blazing fast, but software needs to be architected from the ground up to take full advantage of the….
0
42
0
Week one hacking on search @turbopuffer and I’m shocked: the write:read ratio is way higher than OLTP. Ingesting and indexing a constant stream of massive batches is heavy on writes. Reads are less frequent—they just need to be fast.
0
0
19
RT @turbopuffer: last week team tpuf welcomed two more p99 database engineers @natevanben and @danhhz ❤️🐡💨.
0
2
0
Sign you’ve spent too much time recently with weak iso levels: when trying to recall why consensus requires two durable writes, the prepare phase of paxos starts to look suspiciously like an optimistic, quorum-replicated SELECT FOR UPDATE lock to avoid lost updates (break safety).
2
1
4
RT @ajwerner: Ever wanna just know if a line of code is being hit? Or how often? Or from where? In prod!?. We've been hard at work making t….
0
6
0
RT @largedatabank: I couldn't be more proud of the many teams that contributed to making possible this incredible testament of @DoorDash's….
0
6
0
The next step is end-to-end low-latency serverless apps spread across the globe. One combination I'm excited about is @vercel + @prisma + @cockroachdb.
0
0
6
We actually just found out that our paper describing the work was accepted to the SIGMOD'22 industry track!.
2
0
7
Great thread. Geo latency necessitates a reimagining of infrastructure. Compromising on survivability/correctness of state isn't the answer. My team @CockroachDB spent 2 years addressing this head-on by letting apps express access locality in their schema
Latency is increasingly important across variety of use cases. For example, in e-commerce, going beyond single digit millisecond latencies is believed to hurt revenue. But how is this need for speed driving infrastructure changes today?. Here's one answer. 🧵 1/.
1
2
18
RT @largedatabank: hey cool @CockroachDB is on the top of @GitHub Trending today for some reason!⭐️. .
0
8
0
RT @felixge: I'm very excited to share what I've been working on at @datadoghq recently. ✨ Connecting Go Profiling With Tracing. https://t….
0
28
0
RT @largedatabank: so uh. @Twitter banned @CockroachDB on its 7th birthday for being under 13 years old 😢. it's nice to know that they're p….
0
24
0
RT @prisma: 🪳 Today we're expanding the range of Prisma compatible databases with Preview support for @CockroachDB!. Join our "What's new i….
0
10
0
RT @Nate_Stewart: @CockroachDB is reaching escape velocity! We’ve just raised $278M at a $5B valuation. How did we get here? What's next….
0
25
0
RT @CockroachDB: 🎉 Announcing CockroachDB 21.2. This release extends our capabilities to:. • Integrate more seamlessly with event-driven da….
0
6
0