[jgalt212]

> I also think community and industry enthusiasm around Postgres is at an all time high. There are more managed hosting options than ever (Crunchy Data, Render, Fly.io, and on and on), deep extensions like PostgresML, Citus and Timescale, serverless options like Neon, and real-time services like Supabase with Postgres at their center.

Please sell me why you'd use one vendor to host your DB and another one to host your app. If they are in different racks (forget about different data centers), that's going to kill you on latency. The only way around that we've seen is to vectorize all your queries.

[jtc331]

If deploying on different racks is that big of problem for your latency then you’re severely limited in how far you can scale your application just by physical rack space. IME this just isn’t true.

[jtc331]

And even if in different data centers (say different AZs), query latency is probably 1ms; in practice that’s quite low. How many queries are you doing in a request?

[jgalt212]

> query latency is probably 1ms

> This generally produces single digit millisecond roundtrip latency between AZs in the same Region.

https://aws.amazon.com/blogs/architecture/improving-performa...

So we're both wrong.

[brightball]

Crunchydata deploys in AWS, GCP or Azure if I recall correctly.

[durkie]

Yep, they do. Currently using them on AWS and pretty happy.

[ris]

Ditto aiven.