Embarc-ing on Ruby on Rails
Embarc has long been a Java Web Development shop. Citing our preference for open-source technology built for an open-source and predictable, stable target Operating System in Linux, we’ve developed many scalable and enterprise-level web applications using J2EE Java.
Now, we are considering changing our approach regarding web development technology. Instead of Java, we’re starting to work with Ruby on Rails (aka RoR, or simply – Rails). We’re contemplating this shift based on a number of measurable benefits Rails has over Java. However, the technical aspects of this debate are not the focus of this article. Rather, I’m focusing on explaining the benefits to a non-technical audience. Often times, it’s difficult to explain the pro’s and con’s of a technology decision to people without a strong background in the web development field. In the worst case scenario, it can be perceived as a religious debate that has no clear benefit to the business. Here are some points to raise that might make a decision to begin a Rails project more palatable to the Business Owner of your projects.
- Pure Web Technology: Rails was built to make websites. Other languages such as Java and .NET can be used to write console applications, system functions, and software for other non-Internet related purposes. Rails has a single purpose and is geared to be the best at it.
- Smaller Footprint: Rails aims to increase the speed and ease with which database-driven web sites can be created and offers skeleton code frameworks from the outset. Many of the packages needed to create web applications in Java or .NET are inherent in Rails. It comes out of the box.
- Resources: It’s been no secret that good Java Web developers in Massachusetts are hard to find. Also, when you find them, they may or may not know the “rest” of the internet technologies – HTML, CSS, Apache, Tomcat, etc. Because Rails is a pure web technology – you are only attracting people who inherently are the perfect fit for the organization.
- Latest and Greatest: There are instances I am personally aware where smart, energetic, and rock-star level Java Developers take a pay cut from previous jobs in order to work with Rails. In other words, smart people in this industry are flocking to opportunities work on Rails. By moving to Rails, I feel we’ll have a steady stream of eager beavers, expertly knowledgeable in the web.
- Compatible with Java: Through the use of an interpreter called JRuby, Ruby can be tightly integrated with Java to allow the embedding of the interpreter into any Java application with full two-way access between the Java and the Ruby code.
While Ruby on Rails might be a new phrase for some, it is not new in this industry. Several companies are using Rails to build enterprise-level, profitable products:
- 37Signals.com – They have built a suite of online applications that serve as workflow and data repositories. Go to the site and see their suite of applications:
a. Basecamp (like Embarc’s CMS)
b. HighRise (like Salesforce.com)
c. Campfire (like Skype)
d. Backpack (like Google pages) - Twitter.com – A blogging service, Twitter’s userbase numbers in the millions. Prominent Twitter users include U.S. presidential candidates John Edwards and Barack Obama.
- Eons.com – Eons is a 50+ media company inspiring a generation of boomers and seniors to live the biggest life possible. Founded by Jeff Taylor, founder of Monster.com, Eons was launched in July 2006. Susan Sarandon came to the Charlestown Navy Yard to officially launch the site. Good times were had by all.
At the end of the day, the pro’s and con’s of Rails vs. Java vs. .NET vs. PHP can and will be debated hotly. Don’t lose site of the fact that web technology is just a tool – it must be put in the hands of a talented, intelligent web development team to use effectively.
All business reasons for switching to rails really stem from one basic reason: Faster Development Cycles
Rails makes developing faster.
less time to develop means more time for:
– writing tests to ensure reliable bug-free code
– writing documentation to ensure maintainable code
– collecting customer feedback more often during the development process
– quality assurance testing
– more feature development
Or, it can simply mean cheaper. And not just cheaper in the short term, but cheaper in the long term when you want to go back and make changes to what you already have.