architecture, Layers and Repository Pattern
Posted on 2011-05-03
I know it's a broad spectrum, but I hope you can help.
I'm implementing an small application for learning purposes, but I'm not sure if I'm understanding all the terms/definitions correct.
let's see, I have the following Projects
the MVC-Project (UI)
the Entitiy-Project with all entities
the Data-Project consisting of the Entity-Framework Model and the repository
the Business-Project which handles business logic
so, if you would seperate into different layer, it would look like this:
Data Access Layer
- Data Project
Domain Layer/Business Logic Layer
- Entitiy Project
- Business Project
- MVC Project
is this correct?
Is a Service Layer the same as a business layer?
when using the Repository Pattern, you do not create repository for every entity right?
Instead you create aggregates, which handle multiple entities
handles Persons and PersonAddresses
Does it make sense to have a entity project and a business-logic-project?
I actually could merge them, couldn't I?
if I leave it in two projects entitiy-project would consist of simple DTO's and
I would have to create a Business-Class for every entity, right?
So, I know those are many questions :-)
Hope you can help.
I'm working with VS2010 and .NET 4.0 (C#)