Ok I’ll admit that I mostly skimmed this article :
TheServerSide.com - Hibernate vs. Rails: The Persistence Showdown
I don’t do Java - so it’s not like I’m going to be working with Hibernate any time soon.
This crash course in the difference though gives me two great insights into Rails (Which I’ll have to confirm over the next few weeks)
1. Rails is built around ActiveRecord pattern. To be honest that works great when things are simple - but I already have a couple of apps that out grew that - it does how ever explain how Brett was able to build everything so fast and automagically.
2. Hibernate uses Identiy Map,Data Mapper, Unit Of Work. What can I say - I’m such a big fan of these patterns I actually implemented them from scracth in PHP. The good news it - it was pretty easy to do it in a dynamically typed language like PHP - and with Ruby real Object model it should be even easier to work with.
Now I’m offically intrigued.
Leave a Reply
Moderation Active: Old stuff here... Therefore your comment on this post will be moderated (i.e. don't submit twice !)