[craigkerstiens]

FWIW, managed providers can fully plug into fly just fine. Here's actually a profile of performance times [1] of Fly with various providers and configurations, along with a repo [2] to reproduce/create the same setup yourself.

1. https://webstack.dancroak.com/

2. https://github.com/croaky/webstack

*Disclaimer I work at one of those fully managed database providers.

[samwillis]

I would love it if Crunchy Bridge was available on Fly. Have you considered offering it alongside the other clouds you run on?

I could see a Crunchy Data managed version of Fly Postgres's doing super well. Combining the best aspects of both your experience managing HA Postgres and backup, with the distributed read replicas from Fly.

[Scarbutt]

Why are the response times (api checks) so high?

[lukeasrodgers]

Yeah those response times are in the realm of “why would I even consider that”. If I am trying to tune my db queries to have p95 latency of 1ms (for example) there’s no way I would choose an architecture that then threw that all out the window with ~100ms network latency. Hopefully I am misunderstanding those numbers somehow.

[sb8244]

I saw this earlier and thoroughly didn't understand what is going on with that. I can't make any sense of why that would be so high.

Feels like a better test would be for the healthcheck to time the query RTT and report that back. Completely remove the web request from the equation.

[ngrilly]

Would be interesting to see the request-response round trip time between the Go service and the SQL database, for each combination.