Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ruby Clouds: Engine Yard Vs. Heroku

Posted by samzenpus on from the silverest-lining dept.

snydeq writes "InfoWorld's Andrew Glover provides an in-depth comparison of Engine Yard and Heroku, two cloud-based, platform-as-a-service offerings for Ruby development. 'To put it simply, Heroku will appeal more to developers and Engine Yard will appeal to operations folks. Consequently, when evaluating the two platforms, one's choice usually comes down to what's more important: Heroku's rapid deployment via a hands-off infrastructure, or Engine Yard's total control over all aspects of application deployment, provisioning, and monitoring.'"

3 of 41 comments (clear)

  1. Re:Ruby?! by matthewmacleod · · Score: 5, Insightful

    Literal nonsense - how can a language be crippled without a framework written in it? There are other web frameworks for Ruby, and it's perfectly usable as a standalone language with a nice big library. Ruby's a great scripting language, much like Python: concise, flexible and readable. The off-the-shelf interpreter can be slow, but that's improving and there are alternatives. So what's horrible about it?

  2. Try out openshift by Anonymous Coward · · Score: 5, Informative

    While I am a fan of both of these services, I really enjoy using openshift more. OpenShift is completely free and supports ruby, python, perl, java, and PHP.

    For those who don't know, OpenShift is Red Hat's free platform as a service all running on top of RHEL.
    --

  3. Manga by Anonymous Coward · · Score: 4, Funny

    I admit I am not a big follower of Japanese manga, that's why I probably never heard of Ruby Clouds: Engine Yard vs. Heroku, but is it any good?