#Orm
6 notas · última:
TypeORM: Object-relational mapping with Node.js
The article explains what an ORM is, why it helps with data-driven API work, and how TypeORM brings TypeScript support, decorators, and multiple ORM patterns to Node.js projects.
ORM Is an Offensive Anti-Pattern
The article argues that ORM breaks object-oriented design by splitting data from behavior, exposing SQL throughout the app, and making tests harder. It proposes SQL-speaking objects as the alternative.
Orm Hate
Martin Fowler argues that ORM tools solve a hard in-memory/relational mapping problem, so complaints about complexity and leakage miss context. He favors using them with realistic expectations, or avoiding the problem when the model fits other approaches.
Object-Relational Mapping is the Vietnam of Computer Science
Jeff Atwood agrees with Ted Neward that ORM has no clean solution. Every workaround involves painful trade-offs, and the costs often show up only later in development.
Large Model Problems Continue to Plague Entity Framework, NHibernate
The page says Entity Framework gets much slower as EDMX models grow, and that NHibernate shows similar slowdowns when change tracking and relationships are involved. AsNoTracking is mentioned as a workaround with limits.
Why ActiveRecord Sucks - Very Good Indicators
The post says ActiveRecord is useful, but its convenience comes with memory overhead, tighter coupling, weaker SQL for complex queries, and less readable code when queries get intricate.
