Heroku Dynos Unable to Start • Hacker News Board

Re: Heroku Dynos Unable to Start

#21

Post by GVIrish » Mon, Jun 23, 2014, 9:00 PM UTC

sparkman55 wrote: post #18

alrs wrote: post #16

Earlier quoted context omitted.

I disagree, strongly. If you've architected for IAAS you have sufficient redundancy and a plan for graceful degradation. I'd rather be dealing with an outage after lunch than at 4am.

This is exactly the "developer-centric" mindset that is, frankly, misguided. Sure, I would rather deal with an outage during business hours, but that means that many of my Customers are also dealing with an outage. If the outage were at 4 AM, most of my Customers would be asleep, and wouldn't even notice the outage.

You don't need to make your developers work a 24 hour cycle to do off hours maintenance. You plan ahead, give the team doing the update the day off before and give them a reasonable window to work with.

Maybe I'm wrong but if a deployment goes wrong at peak hours it's going to amount to a lot more lost money for the customer than it will if a deployment goes wrong at off hours. If you cost your customers money with an outage they're not going to care that you scheduled a developer-centric maintenance window.

Re: Heroku Dynos Unable to Start

#22

Post by sparkman55 » Mon, Jun 23, 2014, 9:03 PM UTC

alrs wrote: post #19

sparkman55 wrote: post #18

Earlier quoted context omitted.

This is exactly the "developer-centric" mindset that is, frankly, misguided. Sure, I would rather deal with an outage during business hours, but that means that many of my Customers are also dealing with an outage. If the outage were at 4 AM, most of my Customers would be asleep, and wouldn't even notice the outage.

If you want NASA reliability, build a NASA-grade 24/7 operation across three timezones. If your plan is just to have the nerds skip sleep periodically, you're an asshole.

Exactly! Heroku should be building that 24/7 operation so I don't have to. Isn't that the whole point of PaaS?

Re: Heroku Dynos Unable to Start

#23

Post by alrs » Mon, Jun 23, 2014, 9:10 PM UTC

sparkman55 wrote: post #22

alrs wrote: post #19

Earlier quoted context omitted.

If you want NASA reliability, build a NASA-grade 24/7 operation across three timezones. If your plan is just to have the nerds skip sleep periodically, you're an asshole.

Exactly! Heroku should be building that 24/7 operation so I don't have to. Isn't that the whole point of PaaS?

I'm sure that's the plan. But if you really really really need faultless 24/7 you're looking for something akin to "NASA as a service", and I assume that such a service wouldn't be able to invoice using something as pedestrian as a credit card.

Re: Heroku Dynos Unable to Start

#24

Post by jack9 » Tue, Jun 24, 2014, 3:19 PM UTC

Seriously, why do people use Heroku? Every developer bone in my body says "run away" from the design of the tools to the interfaces to the app build scripts (?really) to the reliability. I'm not saying that AWS/hosted is better, except that they all are, by comparison.