Heroku vs Engine Yard

When it comes to providing PaaS hosting solutions for Ruby development, Heroku and Engine Yard are the de facto leaders. And they both utilize Amazon’s EC2 as a hardware base. However, they also take different paths to get there – Heroku offers isolated slices of EC2 instances, called dynos, that offer very limited access to the underlying infrastructure. Engine Yard offers a curious PaaS-IaaS hybrid; you have much more access to the underlying VM, you get a full EC2 VM to work with, but at the same time you also get an ready-made environment for application development. Let’s peek under the hoods of both solutions.

Filed under: cloud, Heroku

Heroku vs AppEngine

Cloud computing is no longer the next big thing. As evidenced by all the cloud infrastructure and data centers now being set up by established players like Google with its AppEngine and Amazon with AWS, it is the current big thing. Into this mix are some smaller pioneers like Heroku, started all the way back in 2007 – in cloud computing that’s the late Jurassic period. Let’s compare two PaaS offerings, Heroku and Google’s AppEngine, and see what makes each of them tick.

Filed under: cloud, Heroku

Heroku vs EC2

With the increasing importance of cloud computing, services like Amazon’s EC2 on AWS and Heroku are coming under more scrutiny. Even better for the consumer, the increasing number of such services means more choice in the market. But with this increased choice comes an increased level of confusion, because it’s often difficult to do an apples-to-apples comparison of the various services. Even worse, their offerings aren’t strictly in the same domains, but let’s take a stab at it.

Filed under: amazon, ec2, cloud, IaaS, Cloud Computing, Heroku