Sorting out POCO, Repository Pattern, Unit of Work, and ORM
- by CoffeeAddict
I'm reading a crapload on all these subjects:
POCO
Repository Pattern
Unit of work
Using an ORM mapper
ok I see the basic definitions of each in books, etc. but I can't visualize this all together. Meaning an example structure (DL, BL, PL).
So what, you have your DL objects that contain your CRUD methods, then your BL objects which are "mapped" using an ORM back to your DL objects? What about DTOs...they're your DL objects right? I'm confused.
Can anyone really explain all this together or send me example code? I'm just trying to put this together. I am determining whether to go LINQ to SQL or EF 4 (not sure about NHibrernate yet).
Just not getting the concepts as in physical layers and code layers here and what each type of object contains (just properties for DTOs, and CRUDs for your core DL classes that match the table fields???).
I just need some guidance here. I'm reading Fowler's books and starting to read Evans but just not all there yet.