is layerd architecture a patern ? plz guide

Question

User852864959 posted

Hello,

Please guide in typical 4 layed architechture (having User Interface, Custom Types, Business Logic, Data Access Layer) do we follow some design patern ? I am not clear what patern it is or what patern it should be called.

please guide

Answer 1

User-758443495 posted

hi,

first of all if you mean of cutem types is business entities I dont think that it be a layer it should be part of you business logic.

but about your question I think layered, 3tier,4tier, N tierand etc are architect architecture styles that you should use patterns needed in each case.patterns help you to better code in this architecture styles, for example if you have a heavy object that is fixed in the application and you dont need to re construct it like a data access provider you can use singleton,or if you have different caching providers(filebase,memory base,etc) for decision which provider should be used at this time you should use factory or abstract factory

I suggest you to read some architecture resources to better understanding

Answer 2

User220959680 posted

Layered architecture

is architecture approach on 'How you design your application and separate various layers (like UI, Business, Custom and Data access layeres) . Layered architecture makes application maintenance easier and proven.

Video Tutorial:http://scottonwriting.net/sowblog/posts/10660.aspx

 

Desing Patterns

are solution to commonly occuring problems, how you can implement application logic to handle various requirements.

Read more at http://en.wikipedia.org/wiki/Design_pattern_(computer_science)

and here is Microsoft's home page for Patterns & Practices to know more http://msdn.microsoft.com/en-us/practices/default.aspx

Conclusion:- You can download free ebook and read more from http://www.codeplex.com/AppArchGuide

[This guide provides design-level guidance for the architecture and design of applications built on the .NET Framework. It focuses on the most common types of applications, partitioning application functionality into layers, components, and services, and walks through their key design characteristics.]

 

 

Answer 3

User-967169866 posted

That's basically Model View Controller pattern.  MVC.  There's been some adjustments by adding multiple layers, but essentially it's the same thing.

Layer != Tier.  Layer is a software boundary just like the OP stated.  Tier is a hardware boundary such as Data Tier would refer to the database, and the Data Layer refers to the DAL.