And we're back.
ish.
Deliveroo's error message is on point.
Elevated error rates on applications and deployments
21–30 of 76 posts
Re: Elevated error rates on applications and deployments
#22Earlier quoted context omitted.
Heroku was acquired by SalesForce, and like everything Salesforce touches, it'll slowly descend into a steaming pile of
So far it seems that Salesforce is leaving them alone to run their own business
They're one of the only acquisitions that have been kept running pretty much the same way.
There was no integration with force.com or anything like that. I don't think they're even colocated in SFDC datacenters, I think they still run on AWS
Re: Elevated error rates on applications and deployments
#23This 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…
Elasticbeanstalk is a huge mess when you look at its guts. Deployments aren't any better than Heroku either.
Re: Elevated error rates on applications and deployments
#24This 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…
Speaking from the perspective of someone getting small projects off the ground, the value of Heroku (and similar) is that they help you stay focused on dev rather than ops.
In your example of security, you take an increased risk due to attacks on shared services, but I'd suggest that only a small fraction of "production" apps can field as qualified security teams as Heroku can provide... so if Heroku's customers all moved to EC2 there'd be an increase in badly managed and unpatched instances.
Re: Elevated error rates on applications and deployments
#25Down 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).
Re: Elevated error rates on applications and deployments
#26This 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.
Re: Elevated error rates on applications and deployments
#27I got my first SMS alert notification from Pingdom about 55 minutes ago now. One or two requests managed to reach through the the application logs in the last 10 minutes, but still mostly down.
Re: Elevated error rates on applications and deployments
#28This 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…
I'm using Heroku right now and have thought about switching to EC2 as it would save me a bit of money. But the reason I haven't is simply time. Heroku's Pipelines feature, integrated with GitHub, means I get review apps and automatic deploys on merge, just by clicking a few buttons. Now I know this is completely doable with AWS but the time to set it up and switch would be more than it's worth right now.
I don't see Heroku as a very long term solution for us but for the time being, while still a one-man tech team, it just means one less thing I need to deal with. Until I do ...
Re: Elevated error rates on applications and deployments
#29I got my first SMS alert notification from Pingdom about 55 minutes ago now. One or two requests managed to reach through the the application logs in the last 10 minutes, but still mostly down.
Seems to be resolved now...
Re: Elevated error rates on applications and deployments
#30This 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…
I wrestled with Elastic Beanstalk 10 months ago for 2 days and had to give up in the end. Every deploy was dog-slow. And I was trying all kinds of things, imagine the frustration. Only certain versions of software are supported, though I downgraded just to test EB. But I still couldn't get it running in the end.
I can't recall a single time I had a problem deploying to Heroku, including the first deploys. Heroku is lightyears ahead of EB. Speaking of deployment, I might try Convox sometime in the future.
OTOH you can use RDS with Heroku, just be careful to have them in the same region.