...is Entity EJBs. If you've been exposed to them (I hope not) then you'll agree that Hibernate is far, far lighter weight.
Plus the Java community seems to use "lightweight" when referring to systems that manipulate Plain Old Java Objects (POJOs, since Martin Fowler felt they deserved an acronym). That's a useful distinction but overloading "lightweight" to do it probably isn't the best implementation.
I like Class::DBI, and use it, but Hibernate can map much more complex table relationships and handle a whole range of operations that you can't currently do in Class::DBI without resorting to writing the SQL in your objects. It also generates very tight SQL which you would be hard-pressed to beat by hand.
The Advantages of Java (Score:1)
Obviously, it's more scalable, for definitions of the word that include nothing more serious than hand-waving.
the "compared to"... (Score:2)
...is Entity EJBs. If you've been exposed to them (I hope not) then you'll agree that Hibernate is far, far lighter weight.
Plus the Java community seems to use "lightweight" when referring to systems that manipulate Plain Old Java Objects (POJOs, since Martin Fowler felt they deserved an acronym). That's a useful distinction but overloading "lightweight" to do it probably isn't the best implementation.
Hibernate has many more features (Score:1)
Re:Hibernate has many more features (Score:2)
Re:Hibernate has many more features (Score:1)