Comments on: Heroku to Exit Beta, Start Charging for Cloud Computing http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/ Fri, 10 Feb 2012 21:40:26 +0000 hourly 1 http://wordpress.com/ By: The State of Cloud: Startup Heroku Now Hosting 40,000+ Apps http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208828 Mon, 23 Nov 2009 18:31:22 +0000 http://gigaom.com/?p=46958#comment-208828 [...] co-founder James Lindenbaum as CEO. Heroku, which offered its services for free during its beta, started charging for its platform back in April. Sebastian stopped by our offices to give us a quick update on the state of [...]

]]> By: Rajeev Kutty http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208827 Fri, 24 Apr 2009 18:28:15 +0000 http://gigaom.com/?p=46958#comment-208827 I agree with Michael on this one, as more and more enterprises look at deploying their applications on cloud, the selection of ‘the cloud’platform will be influenced by

1) Backward compatibility (ease of implementation, learning curve,etc…)
2) Degree of lock-in (It is not just the cost factor!)
3) Scalability, Performance & Security
4)Total cost (surprise!, indeed it is NOT the first thing to consider)

Heroku still has its work cut out, but Google just got a step closer with its support for Java. I am also curious about level of support and escalation process when multiple clouds are involved.

]]> By: Michael Mullany http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208826 Fri, 24 Apr 2009 17:23:42 +0000 http://gigaom.com/?p=46958#comment-208826 It seems to me that the really big question here is which approach is going to win in the market:

A) the cloud approach that Amazon and Engine Yard are taking — which is you need to bend over backwards to ensure “backward compatibility” meaning that in order to attract customers to your platform, you have to make sure they can re-use the code and technologies that they’re used to using.

B) the cloud approach of heroku and google app engine — which is that everything is fine as long as you re-write everything you need in pure ruby/java/python and run it on top of Google’s runtime (or Heroku’s dyno).

In software history, not having a backward compatibility strategy has always been a recipe for failure.

]]> By: Heroku Out of Beta - Fast, Easy & Cheap Ruby Hosting « Sazbean http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208825 Fri, 24 Apr 2009 17:13:15 +0000 http://gigaom.com/?p=46958#comment-208825 [...] Heroku to Exit Beta, Start Charging for Cloud Computing (GigaOM) [...]

]]> By: Derrick Harris http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208824 Fri, 24 Apr 2009 08:51:48 +0000 http://gigaom.com/?p=46958#comment-208824 It’s not so much the app layer as it is about the data layer. Unless something has changed, App Engine still includes BigTable as the default database, whereas Heroku uses SQL. An app written to leverage BigTable certainly couldn’t be transported to any other platform without some changes being made.

That’s not to say one approach is better than the other, though. Anyone who wants to work with Python or Java, or to take advantage of BigTable, might consider any potential Google lock-in worth outweighed by the benefits of the platform. For its part, Heroku acknowledges that its open-source, best-practices approach does leave it subject to effortless customer abandonment, so it relies on the customer experience to keep them on board.

]]> By: Cloud Computing Links April 23, 2009 at Cloud Curious http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208823 Fri, 24 Apr 2009 03:43:51 +0000 http://gigaom.com/?p=46958#comment-208823 [...] Heroku to Exit Beta, Start Charging for Cloud Computing – GigaOM [...]

]]> By: jamesyi http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208822 Fri, 24 Apr 2009 03:09:37 +0000 http://gigaom.com/?p=46958#comment-208822 also, by putting heroku on top of ec2, youre increasing the number of points of failure, which if youre trying to run a scalable and reliable webapp, youre now relying on both ec2 and heroku being up and running. i think this is the hidden danger of cloud copmuting, is that you start to not know how many layers youre dealing with, and if any of those layers goes away, youre screwed.

]]> By: jamesyi http://gigaom.com/2009/04/23/heroku-to-exit-beta-start-charging-for-cloud-computing/#comment-208821 Fri, 24 Apr 2009 03:07:16 +0000 http://gigaom.com/?p=46958#comment-208821 confused…what about appengine isn’t as open as this solution? particularly with the java version that was just released, they implemented almost all the standard java classes, and all the other stuff they implemented is supported by jrs standards. in fact, i watched the video from their campfire, and they took the code running in appengine and copied it over to ibm websphere without changing a line of code.

sloppy reporting, you should check your facts and publish a correction.

]]>