3 ms·
They're related but distinct problem spaces. Craig Kerstiens is somewhere else on this thread talking about the work that went into Heroku's Postgres. Paul Copp
by tptacek 3y ago
They're related but distinct problem spaces. Craig Kerstiens is somewhere else on this thread talking about the work that went into Heroku's Postgres. Paul Copplestone can give you an earful about how hard Supabase was to build. We can talk your ears off about orchestration and Anycast networking. These are all big problems; they're not just features.
I vividly remember hanging out on my back porch with Kurt as we were plotting out attached storage (we didn't even start out with storage!) and him telling me how hard it would be to replicate the kind of work Craig and Paul had done --- he'd know, after doing Compose.io! We had no illusions that we were going to provide that.
Instead, we charted out a halfway point: "automated" but not "managed" Postgres, which is almost (not quite) just an application you deploy on top of Fly.io. You can see from my sibling comment how well that went. A managed database practice monitors and intervenes with database clusters in ways a fire-and-forget automated system doesn't. If you don't do all that work --- a whole (huge) company's worth of work --- you break peoples expectations, and they question your pedigree on message boards. :)
- swyx 3y agojust here to say i love how well you take criticism. increases trust a lot because you are self aware yet provide a lot of competency proof points. you dont need it but thank you for what you do.
- tptacek 3y agoThank you! The team here gives us a lot to work with. Also: people dunking on us aren't wrong! We've made bets that represent particular spots on all sorts of reliability/predictability/performance/complexity axes. They are what they are, and it would be freaky if all of them paid off. We're wrong about some of this stuff. All we can do is be honest about what we're going for, and how that's going.