3 ms·
At the end of the day you're still doing object relational mapping.You just built something custom instead of using Hibernate,so you're still using an ORM. You
by aikah 12y ago
At the end of the day you're still doing object relational mapping.You just built something custom instead of using Hibernate,so you're still using an ORM.
Your domain objects are still a graph that need to be hydrated from the database. And dont tell me that writing hydrators by hand is fast and dry,especially when you have 100+ domain objects,compared to a few XML files or annotations that can later take advantage of query builders or HQL.
- deleted 12y ago[deleted]
- sudowhodoido 12y agoFair point but it's a terribly light ORM behind an abstraction boundary that doesn't make assumptions about the type of store it is communicating with. We don't write any hydrators. On our previous solution they are generated at compile time. Then they were replaced by runtime code generation inside Dapper. There is no XML, there are no query builders, there is no HQL. There are too few guarantees in each of those technologies.