An Enterprise Approach to our Community Framework

A layered architecture versus a non-layered architecture

Not every application needs to be built in a heavily layered manner. Not every application needs to be overly extensible. Some applications need to be built quickly and simply for the sole purpose of getting them out the door. However, be careful not to build something simple when something flexible should have been built in its place. While you can easily grow an application that was built with growth in mind, extending an application that was built without growth in mind can be difficult, if not near impossible.

Knowing that our application is going to be a large undertaking that should last for some time, we need to design something that can be easily extended as the need arises. For that we will try to design this application with extensibility in mind. The easiest way to do that is to follow the general rule of maintaining "separation of concerns".

Note

Separation of concerns (SoC) is the process of breaking down your application...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

ASP.NET 3.5 Social Networking

By : Andrew Siemer

ASP.NET 3.5 Social Networking

By: Andrew Siemer

Overview of this book

A layered architecture versus a non-layered architecture

Note

ASP.NET 3.5 Social Networking

By : Andrew Siemer

ASP.NET 3.5 Social Networking

By: Andrew Siemer

Overview of this book

A layered architecture versus a non-layered architecture

Note

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access