1-Tier Architecture
We all know software packages like MS Access, MS Excel.They all have the same in common that they access files directly. This means that the file you want to work with must be accessible from a local or shared drive. This is the simplest of all the architectures, but also the least secure. Since users have direct access to the files, they could accidentally move, modify, or even worse, delete the file by accident or on purpose.So 1-tier architecture is simple and cheap, but usually unsecured and data can easily be lost if you are not careful.
2-tier architecture is used to describe client/server systems where the client requests resources and the server responds directly to the request, using its own resources. This means that the server does not call on another application in order to provide part of the service.In 3-tier architecture, there is an intermediary level, meaning the architecture is generally split up between:The application server (also called middle ware).
We all know software packages like MS Access, MS Excel.They all have the same in common that they access files directly. This means that the file you want to work with must be accessible from a local or shared drive. This is the simplest of all the architectures, but also the least secure. Since users have direct access to the files, they could accidentally move, modify, or even worse, delete the file by accident or on purpose.So 1-tier architecture is simple and cheap, but usually unsecured and data can easily be lost if you are not careful.
2-tier architecture is used to describe client/server systems where the client requests resources and the server responds directly to the request, using its own resources. This means that the server does not call on another application in order to provide part of the service.In 3-tier architecture, there is an intermediary level, meaning the architecture is generally split up between:The application server (also called middle ware).
Comparing both types of architecture
2-tier architecture is therefore a client-server architecture where the server is versatile, i.e. it is capable of directly responding to all of the client's resource requests.
In 3-tier architecture each server is specialized with a certain task (for example: web server/database server). 3-tier architecture provides:
In 3-tier architecture each server is specialized with a certain task (for example: web server/database server). 3-tier architecture provides:
- A greater degree of flexibility.
- Increased performance, as tasks are shared between servers
As more users access the system a three-tier solution is more scalable than the other solutions because you can add as many middle tiers (running on each own server) as needed to ensure good performance (N-tier or multiple-tier).
Security is also the best in the three-tier architecture because the middle layer protects the database tier.
There is one major drawback to the N-tier architecture and that is that the additional tiers increase the complexity and cost of the installation.
No comments:
Post a Comment