Pros and cons of Rails 2.0
What do you consider the strengths and weaknesses of Rails 2.0?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The core strength of Rails 2.0 is better synergies with HTTP, and thus by extension, REST. The individual improvements are too numerous to mention here, but suffice it to say that you can get as deep as you want with HTTP using Rails 2.0, including support for HTTP security and many other capabilities.

Perhaps the greatest weakness of Rails 2.0 is the religious way the Rails team favors REST over SOAP. They essentially discourage people from using SOAP, rather than fleshing out better support for SOAP-based interactions. The choice of REST vs. SOAP should be left to the developer or the architect, not the framework.

This was first published in June 2008

Back to top