As much as I like this tooling and the features that Heroku offers it disturbs me that I have to pay $15,000 a month to get more than 99% uptime SLA.<p>To me it is unacceptable to see "max 1 hour downtime" and "max 15 minutes downtime" on plans that cost way more than running your own database on cloud instances from other providers.<p>For reference on AWS I'm running two m3.xlarge instances in an automated failover database cluster that so far has >99.95% uptime for the past year, and it only costs about $400 a month.<p>Meanwhile to get automated failover and a database equivalent to an m3.xlarge you have to pay $1,200 a month on Heroku, and that could still reach 15 minutes of downtime per month.
I suspect this is a response to RDS introducing Postgres support last year [0]. I switched to RDS from managed Heroku DBs at that point because there wasn't enough added value from Heroku to justify the abstractions (plus I wanted to have at least part of our infrastructure not bound up in a single vendor).<p>But these automatic profiling and diagnose features look great, and it can be a headache to find problematic queries in my RDS instance even with tools like NewRelic. I may yet regret moving...<p>[0] <a href="http://aws.amazon.com/blogs/aws/rds-postgres-sla/" rel="nofollow">http://aws.amazon.com/blogs/aws/rds-postgres-sla/</a>
Heroku needs to open source the testing (UPDATE: and data) it has used to claim 3X performance.<p>Adding a single graph for a $2000/mo DB, only performing read only transactions at 30% of its connection limit doesn't sound like putting the DB through its paces, and not real world.
pg:diagnose looks awesome, can I use it on my own Linux server? <a href="https://blog.heroku.com/archives/2014/8/12/pg-diagnose" rel="nofollow">https://blog.heroku.com/archives/2014/8/12/pg-diagnose</a>