Tagged Questions
2
votes
2answers
394 views
Do we achieve 100% Persistence Ignorance solution if we're not using ORM's POCO objects to model the Domain?
Persistence ignorance is ability to retrieve/persist standard objects, where standard objects are considered as classes focused on particular business problem and thus don't contain any ...
16
votes
5answers
674 views
Do ORMs enable the creation of rich domain models?
After using Hibernate on most of my projects for about 8 years, I've landed on a company that discourages its use and wants applications to only interact with the DB through stored procedures.
After ...
0
votes
4answers
243 views
To which layer does this code belong?
When I say "Revisional Data Model", I mean a data model where information is never lost: Deletes never destroy any rows, and updates always cause an insert somewhere else to preserve a row's previous ...
4
votes
3answers
2k views
DDD with ORM where should the business logic go?
I have used an MDA (model driven architecture) tool in the past where we modeled via UML and this generated the business entities (our domain model) and the ORM (mapping etc) amongst other things.
A ...
6
votes
1answer
310 views
Do ORM POCOs replace domain entities?
This is somewhat similar to this question but more broad.
In general, with ORMs like EF 4.1 supporting POCOs, does it now make sense to have your domain entities be the objects that are persisted to ...
5
votes
2answers
270 views
How to define the seams between the domain layer and a database full of stored procedures?
We have a legacy database full of stored procedures.
These stored procedures are somewhat CRUD-categorized but upon inspection of some procedures, they are not "simple" as they might update, delete, ...
