Heroku - Bamboo Routing Performance
blog.heroku.com
Heroku - Bamboo Routing Performance
1–10 of 152 posts
Re: Heroku - Bamboo Routing Performance
#2Interesting -- he seems to be saying that they'll explain all about the problem, but not do anything about it.
Re: Heroku - Bamboo Routing Performance
#3(Wonders what this response would look like if Elon Musk was running Heroku.)
Re: Heroku - Bamboo Routing Performance
#4So the issue only affects Bamboo? that's what it seems to be saying
Re: Heroku - Bamboo Routing Performance
#5Most people are going to come here and mention how they are not planning on fixing the problem.
Put it into context. Heroku made this change 3 years ago, and also has had no issues admitting the change to users. Their documentation has lagged far behind and I believe they will be more transparent in the future. This is an engineering decision they made a long time ago that happened to get a lot of PR in the past 24 hours. Until there is a business reason (losing customers), I don't see them "fixing" the problem.
Re: Heroku - Bamboo Routing Performance
#6Wait, so those guys were on Bamboo, and complaining?
Fuck, that is so not cool.
We've been on cedar ever since it launched, and been running puma threads or unicorn workers. The idea of one dyno per request is bullshit, and I wasn't sure if they were on cedar or not. A dyno is an allocated resource (512mb, not counting db, k/v store etc)
How ballsy of them to complain when they are doing it wrong.
Re: Heroku - Bamboo Routing Performance
#7Interesting -- he seems to be saying that they'll explain all about the problem, but not do anything about it.
I don't think you can really conclude that from this statement, this section could be read to mean they plan on making changes:
"Working closely with our customers to develop long-term solutions"
At this point I imagine they're in damage control mode; I'm not surprised they'd be reluctant to make new promises before everyone's on the same page about the technical issues.
Re: Heroku - Bamboo Routing Performance
#8Interesting -- he seems to be saying that they'll explain all about the problem, but not do anything about it.
I'm sure he doesn't want to commit to anything too soon. This was one of the bullet points:
"Working closely with our customers to develop long-term solutions"
Re: Heroku - Bamboo Routing Performance
#9That's actually a pretty impressive response as far as it goes. Obviously there's no details at this point, but he absolutely takes responsibility, doesn't try to deflect or sugar coat it, and manages to find a tone that is both professional/serious, yet also down-to-earth and earnest. I guess the real impact will be how they go about "making it right" but in terms of a first response to the situation the tone is near perfect.
Re: Heroku - Bamboo Routing Performance
#10Wait, so those guys were on Bamboo, and complaining? Fuck, that is so not cool. We've been on cedar ever since it launched, and been running puma threads or unicorn workers. The idea of one dyno per request is bullshit, and I wasn't sure if they were on cedar or not. A dyno is an allocated resource (512mb, not counting db, k/v store etc) How ballsy of them to complain when they are doing it wrong.
Bamboo is no longer running now.