Let's learn in this post with an example.
We might heard couple of times but never worried about difference between Layers and Tiers, if somebody asks this question, immediately an engineer may think like this,
“I aware about Two-tier, Three-tier and N-tier also involved in implementation of Presentation Layer, Business Logic layer and Data Access Layer but what are the difference between these terms? Or Are all denotes the same only?”
Being as an application engineer you may need not worry about any architectural terms such as layer, tier etc. However, when you became a senior professional or someone involves in application architecture design and architect activities then you should be very clear on this simple basic things.
Alright, let’s start understand what those terms means? and, how each term differs from other one on the application architecture front?
Alright, let’s start understand what those terms means? and, how each term differs from other one on the application architecture front?
For ease of understanding,
- Layer can be defined as logical separation of code, whereas a Tier can be defined as Physical separation of code
- Layer is a way of organizing our code, whereas a Tier is a platform where the code runs.
- In other words, Application can be designed with consists of different layers, and Tiers where that Application layers are deployed.
Here is an example: In the below picture, assume there are servers maintained for "Browser View" as Web Tier, "App Logic" as App Tier and "Data Storage" as Data Tier hosting separately. And, there are three logical layers maintained in "App Logic" tier.
=========================================================
Advertisement: Choosing .NET Core Worker Services OR Windows Services?
=========================================================
Advertisement: Choosing .NET Core Worker Services OR Windows Services?
=========================================================
Comments