As a proof, check out fly.io forums. They are full with posts about suddenly broken Postgres instances.
As a proof, check out fly.io forums. They are full with posts about suddenly broken Postgres instances.
So should many of the people in our forum. This is part of why we wrote this! That said, the vast majority of PG users on Fly have no issues. Most issues are the result of people trying to spend as little money as possible on their underlying infrastructure. When you have a 1GB disk, you'll run it out of space pretty quickly. You may not pay us for it, though, which is what they value most.
We tell people to use CrunchyBridge _all_ the time. It's better than our Postgres for many people.
[edit]
Also other managed DB hosts have similar anti-funnels for pricing, so I'm not trying to pick on Crunchy Data.
2. The 3rd item on there goes to the "pricing" page that doesn't actually tell you the pricing (it says "Starting from $10/mo" but you need to scroll down and click through to get to the actual pricing table) :/
3. The 4th item "pricing calculator" is great; I just didn't find it.
1. https://webstack.dancroak.com/
2. https://github.com/croaky/webstack
*Disclaimer I work at one of those fully managed database providers.
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.
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.
I assume you use SSL, and these are not made on demand (connection pooling ?) On 'cold start' do you get massive latency ?
What kind of latency is there between client and server ?
What made you choose Heroku and not a specific managed postgresql service ?
Did you try flys postgres service?
Yes. I wrote: "I was recently just one of those affected by a random issue!"
I don't notice any measurable latency. Heroku exposes their postgres instances directly on the public web (secured with a strong user/pass combo of course), so there's no difference, networking-wise. There's no additional reverse proxy or some tunnel to route through.
Heroku was the cheapest for the very small instance I needed.
The connections are made on-demand and are insanely fast.