1. Home
  2. Docs
  3. Web Technology I
  4. Web Essential
  5. Client/Server Architecture

Client/Server Architecture

client resposibilities
  • User Interface: The client is responsible for presenting information to the user and receiving user inputs.
  • Request Generation: The client generates requests for services or resources and sends them to the server.
  • Data Presentation: It processes and displays the data received from the server.
server responsibilities
  • Service Provision: The server provides services, processes requests, and manages resources based on the client’s requests.
  • Data Processing: It performs computation, manipulation, or retrieval of data as requested by the clients.
  • Resource Management: The server manages shared resources such as databases, files, or application logic.
Tiers of Client/Server architecture
One tier architecture
  • Simplicity: One-tier architectures are easy to understand and set up.
  • Low Overhead: There is minimal overhead associated with communication between different layers or components.
  • Lack of Modularity: Since everything is tightly integrated, changes or updates to one component may affect the entire application.
  • Limited Scalability: It may be challenging to scale the application horizontally or distribute components across multiple systems.
two tier architecture
  • Client Tier:
    • The client tier is responsible for the user interface, user interactions, and presentation logic.
    • It generates requests for services or resources and sends them directly to the server.
    • The client tier can be a desktop application, a web browser, or any user-facing interface.
  • Server Tier:
    • The server tier is responsible for processing requests, managing data, and providing services.
    • It handles the business logic, data processing, and interacts with databases or other backend systems.
    • The server tier can be a dedicated server or a cluster of servers.
  • Simplicity and ease of implementation.
  • Direct communication between the client and server.
  • Limited scalability as both the client and server functionalities are closely coupled.
  • Changes in one tier may affect the other, leading to tight coupling.
1 sogB55KKa4MK2cjlOtFp5w
  • Client Tier:
    • Same as in the two-tier model, responsible for the user interface and user interactions.
  • Application Server (Middle Tier):
    • The middle tier is responsible for application logic and processing business rules.
    • It facilitates communication between the client and the server.
    • Common tasks include data validation, business rules enforcement, and additional processing before reaching the database.
  • Server Tier:
    • Similar to the server tier in the two-tier model, responsible for data storage, retrieval, and management.
    • Handles database interactions and backend processing.
  • Improved scalability and flexibility due to the separation of concerns.
  • Changes in one tier have less impact on the others, promoting modularity.
  • Increased complexity compared to two-tier architecture.
  • Requires additional infrastructure for the application server.
image 4
image 5

How can we help?

Leave a Reply

Your email address will not be published. Required fields are marked *