Heroku Production Check
blog.heroku.com
Heroku Production Check
1–10 of 19 posts
Re: Heroku Production Check
#2Despite all the hate surrounding Heroku lately, they're doing a pretty good job improving their product for users. This is good.
Re: Heroku Production Check
#3For one of my apps it says that I'm not using a production ready database. I'm using Amazon RDS. How well will the DB add-ons integrate with this check?
Re: Heroku Production Check
#4Despite all the hate surrounding Heroku lately, they're doing a pretty good job improving their product for users. This is good.
I beg to differ. They are definitely releasing a lot of features lately, but I feel that their core product is degrading. There has been a lot of bugs lately with Heroku.
To list a few, right when the whole debacle regarding concurrency started, they had a bug with their scheduler which wouldn't terminate processes. What ended up happening was that customers got billed for processing time they didn't use. Heroku fixed the billing issue after they were told of this issue. There was also a minor security issue where you could grant applications access to heroku via oauth, but you couldn't reject it. Not a huge deal, but it would be nice to revoke apps instead of leaving them out in the limbo. I could probably name off a few more issues I've been having with Heroku, but my point is, I'd rather they spend more time fixing the current issues instead of spinning off new features.
Re: Heroku Production Check
#5Dyno redundancy and DNS CNAMEs to protect the rest of the platform if YOU get DDOSed looks to me like things their customers have to do to compensate for shortcomings of the platform.
That's of course totally ok. What I dislike is how it's being sold as a feature or simple precaution.
Why should I pay double because they have to restart my vm? Why can't they bring up a new one and then kill my current one? Why are they talking about isolating DDOSed customers instead of protecting them?
Again, I can see these issues, but don't sell the workaround as a feature
Re: Heroku Production Check
#6For one of my apps it says that I'm not using a production ready database. I'm using Amazon RDS. How well will the DB add-ons integrate with this check?
Hey, Heroku engineer here. Can you shoot me an email at jonathan [at] heroku [dot] com and I can take a look?
Re: Heroku Production Check
#7Dyno redundancy and DNS CNAMEs to protect the rest of the platform if YOU get DDOSed looks to me like things their customers have to do to compensate for shortcomings of the platform. That's of course totally ok. What I dislike is how it's being sold as a feature or simple precaution. Why should I pay double because they have to restart my vm? Why can't they bring up a new one and then kill my current one? Why are th…
I'm a PM at Heroku. The dyno redundancy check has nothing to do with protecting the platform. It is a best practice for production apps to have redundancy at the web server level. This protects your app from downtime should underlying servers fail, or if the web server process were to crash. N+1 redundancy for the win.
Also, it does not cost customers double because the first dyno is free with each app.
Re: Heroku Production Check
#8Dyno redundancy and DNS CNAMEs to protect the rest of the platform if YOU get DDOSed looks to me like things their customers have to do to compensate for shortcomings of the platform. That's of course totally ok. What I dislike is how it's being sold as a feature or simple precaution. Why should I pay double because they have to restart my vm? Why can't they bring up a new one and then kill my current one? Why are th…
I'm a PM at Heroku. The dyno redundancy check has nothing to do with protecting the platform. It is a best practice for production apps to have redundancy at the web server level. This protects your app from downtime should underlying servers fail, or if the web server process were to crash. N+1 redundancy for the win. Also, it does not cost customers double because the first dyno is free with each app.
Well then that's even more than double, it's from free to paid.
Re: Heroku Production Check
#9Dyno redundancy and DNS CNAMEs to protect the rest of the platform if YOU get DDOSed looks to me like things their customers have to do to compensate for shortcomings of the platform. That's of course totally ok. What I dislike is how it's being sold as a feature or simple precaution. Why should I pay double because they have to restart my vm? Why can't they bring up a new one and then kill my current one? Why are th…
I'm a PM at Heroku. The dyno redundancy check has nothing to do with protecting the platform. It is a best practice for production apps to have redundancy at the web server level. This protects your app from downtime should underlying servers fail, or if the web server process were to crash. N+1 redundancy for the win. Also, it does not cost customers double because the first dyno is free with each app.
So it actually costs an infinite percentage more to run that second dyno ;-)
But I agree your points on redundancy at the webserver level.
Re: Heroku Production Check
#10For one of my apps it says that I'm not using a production ready database. I'm using Amazon RDS. How well will the DB add-ons integrate with this check?
IIRC you actually have to remove the Heroku postgres DB for it to pass if you're running RDS.