Difference between revisions of "Cloud Architecture Design Patterns"
(Created page with " =Architecting on AWS= All applications are broadly divided into two types. These are '''2 tier''' or '''3 tier''' architecture. Basically at high level we can say that '''2-t...") |
|||
| Line 2: | Line 2: | ||
=Architecting on AWS= | =Architecting on AWS= | ||
All applications are broadly divided into two types. These are '''2 tier''' or '''3 tier''' architecture. Basically at high level we can say that '''2-tier architecture is Client server application''' and '''3-tier architecture is Web based application'''. | All applications are broadly divided into two types. These are '''2 tier''' or '''3 tier''' architecture. Basically at high level we can say that '''2-tier architecture is Client server application''' and '''3-tier architecture is Web based application'''. | ||
| + | |||
==Two-Tier Architecture== | ==Two-Tier Architecture== | ||
| + | The two-tier is based on Client Server architecture. The two-tier architecture is like client server application. The direct communication takes place between client and server. There is no intermediate between client and server. Because of tight coupling a 2 tiered application will run faster. | ||
| + | |||
| + | https://qph.fs.quoracdn.net/main-qimg-8ddb5c6744aa408533b8ece69ccf40c8.webp | ||
| + | |||
| + | The above figure shows the architecture of two-tier. Here the direct communication happens between client and server, there is no intermediate layer between client and server. The Two-tier architecture is divided into two parts: | ||
| + | |||
| + | * Client Application (Client Tier) | ||
| + | * Database (Data Tier) | ||
| + | |||
| + | On client application side the code is written for saving the data in database server. Client sends the request to server and it process the request & send back with data. The main problem of two tier architecture is the server cannot respond multiple request same time, as a result it cause a data integrity issue. When the developers are not disciplined, the display logic, business logic and database logic are muddled up and/or duplicated in a 2tier client server system. | ||
| + | |||
| + | '''Advantages:''' | ||
| + | * Easy to maintain and modification is bit easy. | ||
| + | * Communication is faster. | ||
| + | |||
| + | '''Disadvantages:''' | ||
| + | * In two tier architecture application performance will be degrade upon increasing the users. | ||
| + | * Cost-ineffective. | ||
==[[Three-Tier Architecture]]== | ==[[Three-Tier Architecture]]== | ||
Revision as of 09:08, 12 January 2020
Architecting on AWS
All applications are broadly divided into two types. These are 2 tier or 3 tier architecture. Basically at high level we can say that 2-tier architecture is Client server application and 3-tier architecture is Web based application.
Two-Tier Architecture
The two-tier is based on Client Server architecture. The two-tier architecture is like client server application. The direct communication takes place between client and server. There is no intermediate between client and server. Because of tight coupling a 2 tiered application will run faster.
https://qph.fs.quoracdn.net/main-qimg-8ddb5c6744aa408533b8ece69ccf40c8.webp
The above figure shows the architecture of two-tier. Here the direct communication happens between client and server, there is no intermediate layer between client and server. The Two-tier architecture is divided into two parts:
- Client Application (Client Tier)
- Database (Data Tier)
On client application side the code is written for saving the data in database server. Client sends the request to server and it process the request & send back with data. The main problem of two tier architecture is the server cannot respond multiple request same time, as a result it cause a data integrity issue. When the developers are not disciplined, the display logic, business logic and database logic are muddled up and/or duplicated in a 2tier client server system.
Advantages:
- Easy to maintain and modification is bit easy.
- Communication is faster.
Disadvantages:
- In two tier architecture application performance will be degrade upon increasing the users.
- Cost-ineffective.
