←back to thread

Reliability: It’s not great

(community.fly.io)
1226 points bishopsmother | 3 comments | 06 Mar 23 17:47 UTC | HN request time: 0.001s | source
Show context
claytonjy ◴[06 Mar 23 19:27 UTC] No.35046327[source]▶
Very interesting to see Kurt assert theyre going to "solve managed Postgres", and I'm super curious to know what that means. Does it mean something like RDS, or more like CrunchyData?

I could see them building something RDS-like on their own, but if they're trying to go further than that I wonder if they'll buy or partner with other companies rather than doing it themselves. Neon strikes me as a Postgres-as-a-service that could pair well with Fly.

replies(4): >>35046437 #>>35046733 #>>35046890 #>>35047601 #
aeyes ◴[06 Mar 23 21:07 UTC] No.35047601[source]▶
If I was in their shoes I'd probably aim for a "serverless" Postgres experience where you get a connection string and you know nothing else.

I think RDS, Crunchy, Aiven and others aren't quite there yet.

replies(1): >>35048815 #
1. chime ◴[06 Mar 23 22:41 UTC] No.35048815[source]▶
They kind of offer that with their Redis (via Upstash). But for our use-case, we needed it to be managed PG and Redis. Going out of the LAN introduces too much latency.
replies(1): >>35048855 #
2. chronark ◴[06 Mar 23 22:44 UTC] No.35048855[source]▶
Upstash Redis for Fly runs on Fly infrastructure and we observe latencies in the low single digit milliseconds.
replies(1): >>35049347 #
3. aeyes ◴[06 Mar 23 23:28 UTC] No.35049347[source]▶
Maybe that is what Fly had in mind: That some company like Upstash would bring "managed" serverless Postgres to their platform.

Unless somebody natively implements clustering in Postgres I don't see that happening anytime soon, all existing tools require way too many moving parts.

I don't know why they'd even want Postgres for the type of service they are offering, KV or maybe SQLite seem like a better fit.