The N-Layer tier project architecture

There are many ways to split up your solution structure in many layers. My favorite way of doing it is as the diagram bellow describes:

2015-19-03 06-19-54-313

I have:

  • Presentation layer: where my screens/pages are, all they know is how to display data they receive
  • Services layer: where all my business rules are, the services classes are responsible for manipulating data
  • Data layer: where my database access and my database models are
  • Crosscutting: classes used by the entire solution, read more about it on MSDN

Another example which looks very similar is one posted on MSDN

sa-21

This is enough to keep your solution clean and with a clear separation on concerns.

The hint is to avoid complicating what does not need complicating.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s