My hesitation with ORM Technology (and else, actually)
Honestly, I know ORM technology such as Hibernate only from discussion and still not have opportunity to try it my self, but as a conservative guy who has a difficulty to accept new change, I feel that this ORM thing is one of my hesitation to learn deeper about it, but I know someday I have to.
First of all, I think the idea to make and object-based database is nice idea and absolutely will help so many people out there with their project, the idea to bridge the object from relationship database system is also a nice approach, but (ah here you go 
) how long do you think this euphoria would happen? until the database system creator create the object-oriented connector to their system? so this is my simple imagination about ORM:
[ Program with ORM connector -> [ORM Engine] ] -> [RDBMS Data Store]
While SQL has been around for decades(?) it seem fair enough to me if this kind of concept should be embedded within the system it self, think of it, the database system is so mature it has it’s own art to deal with it, and programmers with god power to make a change to database schema on runtime, persist everything on the business computation / production server memory(?), is not a very much a good idea, somehow.
[ Application -> Virtual Machine -> Native Platform ]
hey, I like any 3 tier approach actually I realize that today is a virtualization day, everybody virtualize everybody, computer now is so fast, we don’t sacrifice human to do the dirty work, can’t we? ORM virtualize RDBMS, with one ORM engine we can connect to many BDMS platform out there, good to you, so then what will stop me and anybody else to make another ORM engine? is there any standard already? ah… the standard thing, I guess this is the case, SQL has already the standard fora while, with SQL we can work separated / distibuted server, so what did you think people make it in the first time(?)
So, I always say that good thing for many people maybe not suit for others, and it is all about the people behind the things no matter how sophisticated tools and technology we used. Maybe you share the same opinion with me, I like if the approach to be like this:
[ A well designed program with usual SQL connector ] -> [Managed RBMS Engine -> Data Store]
So I guess the issues here are about how well managed program in the end and overall performance to gain. yeah, I know misused of SQL in the program can be a nightmare, but managed SQL in ORM is also not a fun horror to imagine… But given a super duper server, heavy team workload and a long term project to managed, you bet I don’t have any option today except to join the hip (wordpress stuff ) soon…
Maybe, if it is in the military, the choice is about using a special force small tactical team with highly-specialized trained personels versus the whole batalyon with all the latest equipments, war machines and replaceable trained enough personels on a combat mission… it has its own advantage and disadvantage, your call…
