Logical Architecture

Diagram

Assemblies & Dependencies

Layers

Domain

complete this section.

Infrastructure Providers

complete this section.

Recommendations of Use
  • Whenver you need to make use of an INFRA-STRUCTURAL feature that is identified as NOT business logic and NOT repository access, you probably need to build a new provider. Several providers are available by default in the architecture so, please, DRY.

Infrastructure Repositories

complete this section.

Recommendations of Use

Application Services

Application Services generally aggregate and encapsulate business logic and more fixed business procedures that have no reason to be built using a Workflow (eliminating some of the performance loss related to high level translation of activities designed using the Windows Workflow Foundation http://stackoverflow.com/questions/204754/performance-impact-of-using-workflow-foundation).

Recommendations of Use
  • When your FxCop complains about the rule CA1506 - AvoidExcessiveClassCoupling, try to extract the logic from your controller action and move it to a very semantic Application Service that can orchestrate your business procedure.

Application Workflows

complete this section.

Recommendations of Use

Kernel

This is what ties all your layers together and it is the only assembly that really references all the others within the solution.

Important: Please refer for Ninject and Singleton considerations that are VITAL for the Application.

Recommendations of Use

Last edited Sep 9, 2011 at 6:41 PM by hudsonmendes, version 2

Comments

No comments yet.