3 ms·
We switched off Heroku to AWS Aurora once Aurora came out with a production-ready Postgres offering. We haven’t looked back. On Heroku we used to run up agains
by kareemm 9y ago
We switched off Heroku to AWS Aurora once Aurora came out with a production-ready Postgres offering.
We haven’t looked back. On Heroku we used to run up against their CPU burstability limits and would get throttled. Simple Queries for an indexed field would take 100ms+. Web requests would queue up and customers would have a terrible experience.
The worst part is that Heroku support would often take days or weeks (!) to respond. And we were paying them $500+ per month. When they did, they gave us no insight into when we hit the burstability limits or when we’d be back to normal - the app simply got slow and it was never clear why.
Switching to aurora was fairly painless. And we pay less for a box that’s got roughly 4x the resources, decent management tools, and no burstability limits. It’s been fantastic.
We sent detailed and kind feedback to Heroku before and after switching and got a fairly bland response. Perhaps they couldn’t let us know that these kinds of new Postgres plans were coming, but it came off like Heroku didn’t really care much about the experience we had on their platform.
- akurilin 9y agoHave you experienced any pain-points with Aurora that perhaps you would have avoided by using RDS? We've been thinking of switching over, but some teams reported seeing different performance behavior from their existing queries that in some cases made them roll back.
- kareemm 9y agoHaven’t seen anything negative so far. It’s been a couple months now and super snappy. But perf with Heroku was so unpredictable that Aurora would have to be terrible for us to consider going back.