How Rails Change The Backend Coding Effort
Posted by Guy Naor Sat, 11 Mar 2006 18:08:00 GMT
One thing I lately noticed, is that Ruby on Rails completely changes the work distribuition between the backend and the rest of the system.
In my past projects (C++ on Windows - see my first post), the backend took a significant amount of work just for writing and reading the objects in the databse. When you also take into account all the code needed to set up the connections, handle the associations and other related stuff and DEBUGGING you end up spending 30-40% of the time on the backend.
With rails it goes down to about 5% of the time, leaving much more time for the business logic of the application and the UI.
I just wish we had something as beuatiful and useful as rails for the UI... But hey, a man is entitled to dreams :-)


















what? isn't business logic supposed to reside in the backend?
Business logic does reside on the backend, but my point was regarding the actual grunt work of data access and all that relates to it. I guess I need to be a bit more clear next time...
The business logic is also simplified a lot using rails because of the ease of talking to the backend, but the difference isn't as big as the models for data access and modeling.