Hello everyone! Welcome to the blog. Today, we’re talking about Client-Server Architecture, this is one of the most important topics of System design. So, let’s start. Below is the content outline for this article.
Table of Content
- What is Client-Server Architecture?
- Types of Client-Server Architecture?
- 2 Tier Architecture
- 3 Tier Architecture
- N-Tier Architecture
- Conclusion
- Call to Action
- References
What is Client-Server Architecture?
Client-Server system is an architecture, where a client sends a request to a server, and server responds with the appropriate data/result. It is one of most basic and fundamental concept of System design.
Types of Client-Server Architecture?
Thin Client: Here Server side is processing most of logic and data, meanwhile client is lighter (only used for presenting result to user). Example of this is Netflix or any streaming side, where most of the processing is done at server side.
Thick Client: Here Most of the processing is done at client side. Example video editing software or pc games.
2 Tier Architecture
This architecture contains only 2 nodes. One client, and one server. Server handles logic and data meanwhile client is used for presentation only. Example includes static website or any simple website.
3 Tier Architecture
This architecture contains 3 nodes. One client, One server and One Database layer. Server communicates with Database later to fetch data which is then sent back to Client. Example includes library management system.
N-Tier Architecture
This architecture is used for large scale applications where caching and load balancing is required. This can contain more than 3 nodes as shown in diagram. Examples include Facebook, twitter etc.
Conclusion
Anyone learning system design, this is the basic concept. Client server architecture is one of the most important topic to be understood.
Call to Action
You should learn more about this client server architecture from references below. Additionally, you can create some applications for this.