ORM is an Offensive Anti-Pattern
summary
Claim: ORM is an anti‑pattern because ORM turns objects into dumb data bags, and common tools like Hibernate/JPA produce DTOs with getters and setters that leak state, create hidden coupling and rampant duplication, and wreck long‑term maintainability. Evidence: code samples showing transaction + query + getX/getY + setX/setY, reliance on JDBC and engines, and a suggested alternative that encapsulate persistence inside objects so domain objects own SQL interactions (uses a lightweight query library) and clients just call behavior.
AI-written summary · about
chapters (5)
related talks
48mORM Iinsights - How to Not Hurt Yourself?
50mORM – the tip of an iceberg
59mDoctrine ORM Good Practices and Tricks
23mI Would Never Use an ORM
47mWhen ORM Becomes OMG: Performance Pitfalls in JPA and Friends
25mHow We Prepared Data: ORM and All That
46mJimmer ORM: An Alternative to JPA
01h 05mAdvanced Weapons and Tactics