Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elevated error rates on applications and deployments

status.heroku.com

Post reply on HN
Print view View original

51–60 of 76 posts

Re: Elevated error rates on applications and deployments

#52

Post by pg_is_a_butt »

michaelbuckbee wrote: post #26
benmmurphy wrote: post #16

This is kind of offtopic but what is the attraction of using Heroku over using EC2 directly now. I remember back in the day when EC2 didn't have RDS and Elasticbeanstalk Heroku was an attractive option because you could deploy and scale without needing to do any kind of system administration. But now EC2 is offering managed databases through RDS and elastic bean stalk gives you git style deployment similar to Heroku…

It's still significantly easier to get up and running and keep a system up and running on Heroku than the AWS equivalents.

define "significantly".

elastic beanstalk is about as simple as it gets... choose your platform and upload a zip file or use git deploys. how could heroku be "significantly" easier?

Re: Elevated error rates on applications and deployments

#53

Post by sleepyhead »

gryzzly wrote: post #33
sleepyhead wrote: post #6

Earlier quoted context omitted.

Just like with previous incidents. I understand operating Heroku is not trivial but with 15 minutes after my monitoring systems (Pingdom, New Relic and Logentries) notifies me they need to improve this.

also not the cheapest service and no direct support line…

What are you comparing to cost wise? Please do include costs for setting up and maintenance in that comparison.

As for support I have always found Heroku to respond very quickly. And they do have direct support. https://www.heroku.com/support

Re: Elevated error rates on applications and deployments

#56

Post by ivan_gammel »

spacehunt wrote: post #47
benmmurphy wrote: post #16

This is kind of offtopic but what is the attraction of using Heroku over using EC2 directly now. I remember back in the day when EC2 didn't have RDS and Elasticbeanstalk Heroku was an attractive option because you could deploy and scale without needing to do any kind of system administration. But now EC2 is offering managed databases through RDS and elastic bean stalk gives you git style deployment similar to Heroku…

For sites already using Salesforce, Heroku Connect is quite a time saver. It handles the two-way sync between Salesforce objects and Heroku Postgres for you.

It's not a time saver, unless you are small and one developer works on both sides of integration. Integration through database is an antipattern, because it makes apps strongly coupled and fragile and building an app on top of Heroku Connect database adds extra management and maintenance costs, required to keep both sides in sync.

Re: Elevated error rates on applications and deployments

#58

Post by danielsiders »

babgyy wrote: post #7

What options would you consider if heroku was down permanently ?

(Disclosure: I'm the CEO co-founder of Flynn)

Heroku is a great product and it going down permanently would be a huge loss to the community.

However there are a number of open source alternatives with very similar user experiences that you can run yourself in a variety of environments including:

https://flynn.io/ https://github.com/dokku/dokku http://deis.io/ https://www.openshift.com/

Re: Elevated error rates on applications and deployments

#59

Post by spleen »

aquilligan wrote: post #25

Down for almost an hour now. Haven't seen anything of this scale happen in 18 months or so of running our apps on heroku. Looking forward to the postmortem from Heroku (and hopefully my app being up again).

Do they really release postmortems? I've seen them mentioning postmortems in incident statuses, but I've never actually read one.
Post reply on HN