3 ms·
Many Java developers say ORMs are the problem. Not so. JPA is. It is complicated, has lots of implicit behaviour, has a really bad query language and is horribl
by pieterb8 6y ago
Many Java developers say ORMs are the problem. Not so. JPA is. It is complicated, has lots of implicit behaviour, has a really bad query language and is horrible to optimize.
It is why you never hear 'ORMs are horrible' from ruby on rails or elixir developers: they have a proper ORM!
Actually Java has too, and probably several - Ebean, for example, solves all of the complexity problems, adds a query creation tool that stays very close to SQL and allows very simple object fetching, allows for simple batch operations, and requires a proper explicit save instead of the complicated implicit JPA one.
- nesarkvechnep 6y agoTo be honest, Ecto is not an ORM, it's a query builder with superpowers. More so Elixir is a functional language and technically the O in ORM is missing. I love Ecto, I've never seen something as easy to use and maintain but it's not something Java folks would call an ORM.
- pieterb8 6y agoTrue indeed, certainly not an ORM. But I would say the effect you can achieve with it is very close to what a proper ORM can do, much more so than the lower level frameworks java people are now recommending.