Is there a similar service that is better than Heroku that anyone would recommend switching to?
Depends on your platform... AppFog.com supports a few...
Heroku Class Action
61–70 of 78 posts
Re: Heroku Class Action
#62Attorney 'Values' page includes stock photo of corporate jet. Aaaaand we're done here, folks. http://kristensenlaw.com/values.php
Re: Heroku Class Action
#63Earlier quoted context omitted.
> We don't have the resources right now to get off of the platform quickly, I hear people say this a lot but I believe it comes more from the emotion of fear than a rational consideration of the possibilities. For example, Amazon Elastic Beanstalk now supports Rails deployments that are just as easy as Heroku, and you retain 100% control over the underlying EC2/ELB/etc resources while having a nice management layer t…
Honestly I have not looked into it so far and hope you're right. We also use a number of addons, though I don't think any would be too difficult to replicate. Regardless, it's a significant amount of work for a startup with just a few engineers, perhaps a week of two of distraction. I expect a bunch of "how to migrate off of heroku" blog posts will be out there shortly.
Thanks very much for the blog post idea, I think I'll do something with that!
FYI you can keep all your Heroku addons inside your Heroku account while utilizing them from a server outside Heroku. For example, if you use the "Redis To Go" Heroku addon, you can fire up your own EC2 instance (possibly through AWS Elastic Beanstalk) and connect to your Redis To Go instance using the same connection info. The main difference will be that you won't have access to Heroku's environment variables that you're using now, but you can use a config file instead.
Re: Heroku Class Action
#64My startup is heavily invested in and tied to Heroku. We don't have the resources right now to get off of the platform quickly, but plan to as soon as possible. Like Rapleaf, we have spent an enormous amount of effort optimizing and searching for the causes of latency, and overpay for dynos to reduce but not eliminate the chance of latency issues. Heroku has always told us it's our fault. While I have no interest in…
So, uh, what was the thought process when choosing a PAAS provider? I mean, step back for a moment, and ignore the specifics of Heroku; they are a PAAS provider with no completely compatible competitors, is that not so? Whenever I choose service providers (or choose to outsource services) my first thought is "what happens if I have to switch away from them?" Even if you think my first rule of business is too cynical,…
That's certainly a consideration, but every PAAS is "unique" by definition. Something like Google Apps has more lock-in than others. Some like Heroku are attractive because they have features not available elsewhere that would take a lot of resources to reproduce.
We chose heroku and Rails for the reasons you suggest, and even tried to avoid major tie-ins to the platform. That doesn't mean it's trivial to move to another platform.
Re: Heroku Class Action
#65It is going to be interesting when this gets to discovery, and we find out what Heroku were saying internally this entire time about the issue. There are bound to be internal emails that discuss this issue and what to do (or not to do) about it. For this reason I can see this being settled. Perhaps refunds and an apology.
Re: Heroku Class Action
#66Ok this is going too far. Did Heroku make a mistake? Yes. Did they mislead and lie to their customers? Yes. But is it worth pursuing a class action lawsuit that could ultimately ruin them - if not financially, but force their mgmt team to focus on this damn suit rather than fixing the damn problems? Hells no. I hope RapGenius is not the lead plaintiff in this, otherwise I will be very disappointed. I applaud them for…
Did Heroku make a mistake? Yes. Did they mislead and lie to their customers? Yes. But is it worth pursuing a class action lawsuit that could ultimately ruin them - if not financially, but force their mgmt team to focus on this damn suit rather than fixing the damn problems? Hells no.
Nice template for an emotional appeal you've got there, dawg (seriously, wtf are you going for with the vernacular embellishments)
Your argument justifies malfeasance without penalty for any entity. Swap out 'Heroku' for Monsanto, Microsoft, or banks that launder money for drug cartels and read it again. See if you still buy the reasoning. If misleading and lying to customers (your words) isn't enough for a lawsuit, what is?
(Not saying Heroku is equivalent to any of the above companies, just illustrating the lack of reason in parent post).
Re: Heroku Class Action
#67Earlier quoted context omitted.
They blatantly lied about how a core part of their service worked for years. It was raised to them previously and they didn't change the docs nor the way their system worked. This negatively affected a lot of their customers in many ways (overspending on heroku, time wasted, lost customers and revenue). When Heroku's customers have incurred significant costs and/or losses because of Heroku's false claims, I don't see…
They didn't "blatantly lie"....they lied. They built their product 1 way and it morphed into another architecture as they grew. They made decisions that optimized for their financial benefit, but I wouldn't go as far as to say they "blatantly lied". Let's not get too carried away here. As a long time Heroku user, I was pissed when I heard this...but they have done so much good for my own development career and freela…
Offering, and charging money for, a monitoring tool (New Relic) that doesn't monitor a very important part of the Heroku request cycle is pretty blatant. It was probably pretty profitable too!
EDIT: comma placement.
Re: Heroku Class Action
#68This is why you don't fuck around with PR issues. They can easily turn into lawsuits.
This is America, everything can easily turn into a lawsuit.
Even if Heroku had handled the PR issue perfectly, it's very likely some enterprising lawyer would still be looking to sue.
Re: Heroku Class Action
#69This is why you don't fuck around with PR issues. They can easily turn into lawsuits.
This is America, everything can easily turn into a lawsuit. Even if Heroku had handled the PR issue perfectly, it's very likely some enterprising lawyer would still be looking to sue.
True, but they would not have had to deal with a bunch of pissed off customers.
Re: Heroku Class Action
#70My startup is heavily invested in and tied to Heroku. We don't have the resources right now to get off of the platform quickly, but plan to as soon as possible. Like Rapleaf, we have spent an enormous amount of effort optimizing and searching for the causes of latency, and overpay for dynos to reduce but not eliminate the chance of latency issues. Heroku has always told us it's our fault. While I have no interest in…
Like Rapleaf, we have spent an enormous amount of effort optimizing and searching for the causes of latency, and overpay for dynos to reduce but not eliminate the chance of latency issues. Heroku has always told us it's our fault.
You may well find that running your own ops means you run into exactly the same sort of issues - most companies see multiple major problems with their infrastructure as they scale. Heroku certainly haven't delivered for everyone, and it seems their promises of painless scaling are just not being met when it comes to larger customers, but this stuff is hard, and moving off heroku won't get rid of these problems for you, but it will make them your problems and perhaps give you more of a chance to fix them.
It would be really interesting (for heroku customers and for everyone else) to see a write up of your transition when you do move - it may not be as painful to do so as you anticipate.
Kudos on not recommending a lawsuit, which I can't see helping anyone but lawyers at this point.