Enterprise applications are considered to be complex to design and develop. Technologies such as J2EE and .Net augment this generalization. But there are technologies and frameworks that beg to differ. Ruby is one of those technologies/languages and Ruby-on-Rails (also called RoR) is such a framework.
Ruby-on-Rails differs from other technologies in the aspect that, while other enterprise technologies give more stress on configuration, RoR stresses convention, thus eliminating the need for lengthy configuration files based on XML. The base of RoR being Ruby gives it one more advantage, the advantage of working with a Very High Level Language. Above all RoR natively supports Model-View-Controller architecture.
However the question still remains: how effective and productive is RoR? In the world of web development where every new framework (whether based on Java or any other language) is touted to be the one to revolutionize the web programming paradigm, how can one be sure of authenticity of the claim? In this discussion I will try to present both the sides of RoR and leave the rest to your discretion.
The upcoming section will focus on the recurring terminology in the world of RoR. In the next section I will detail the steps to be followed in creating a database driven application in Ruby-on-Rails. In the last section, a real world data driven application will be created. Thatís the outline for this discussion. Here I am making one assumption, that the reader is already familiar with Rubyís syntaxes and semantics. With this in mind, let's start the discussion.