On Tue, Feb 24, 2009 at 10:33 PM, Seto <[email protected]> wrote:
>
> Hibernate?iBatis?Some other object dbs like db4o?
> What could take full advantage with guice?
> Could someone give me some suggestions?

I wouldn't make my ORM(hibernate/JPA) or SQLMapping(ibatis) decision
based AT ALL in regard to guice. Guice will help a bit with whatever
you choose (I'm using guice now with iBATIS), but definitely don't
base your persistence decision based on guice integration.

The decision of what type of persistence layer to use should be based
on a lot of other factors. Obviously this isn't the forum for a
discussion on persistence layer choices, but I tend to give the advice
of...

If you have to work with a legacy database that is quite large and has
a lot of join tables, I always suggest iBATIS. If it's a brand new
application where the database can evolve with the development of your
application, an ORM solution like Hibernate should be fine. I still
have a bias towards iBATIS in either case, but I'm not really bigoted
to much one way or the other and they really aren't 'true' competing
technologies (iBATIS doesn't claim to be an ORM solution.)

-- 
Rick R

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"google-guice" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-guice?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to