Modular enterprise architecture using MVC and Orchard CMS
- by MrJD
I'm making a large scale MVC application using Orchard. And I'm going to be separating my logic into modules. I'm also trying to heavily decouple the application for maximum extensibility and testability.
I have a rudimentary understanding of IoC, Repository Pattern, Unit of Work pattern and Service Layer pattern.
I've made myself a diagram. I'm wondering if it is correct and if there is anything I have missed regarding an extensible application.
Note that each module is a separate project.
Update
So I have many UI modules that use the db module, that's why they've been split up. There are other services the UI modules will use. The UI modules have been split up because they will be made over time, independent of each other.
