On Wed, Jul 14, 2010 at 11:45 AM, Peter Becker <peter.becker...@gmail.com>wrote:
> On 14/07/10 19:16, Moandji Ezana wrote: > >> The thing I find most useful about Hibernate is that when you have a lot >> of tables of inter-related data, it really alleviates the pain of having to >> think about what data you need to load for each possible workflow. >> > Not if you care about scalability, in which case you really need to know > what you want to fetch and how all your caching layers work (although the > caching as such can be a good feature to have). Particularly if you reach > the same object from different contexts with different requirements, > thinking about eager and lazy fetching can get rather complicated. True, but if you need to scale massively, you probably aren't using Hibernate anyway. (Or are you? Anyone know of massive sites that use Hibernate?) Moandji -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
