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


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.


One thought on “The N-Layer tier project architecture

  1. Christine Hagwood

    “Pi is a non-copyrightable reality, and the transcription of pi to music is a non-copyrightable concept,” Simon wrote in his authorized opinion .
    Mathematics is only attainable because God has created an ordered, law-full, universe that is comprehensible.


Leave a Reply

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

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

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s