Suggest an editImprove this articleRefine the answer for “What is a client-server network?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**A client-server network** is an interaction model in which one node (the server) provides resources or services, while other nodes (clients) request access to them. **Key point:** interaction follows a request → response pattern, and the server is a centralized, always-available node that handles many client requests.Shown above the full answer for quick recall.Answer (EN)Image**A client-server network** is an interaction model in which one node (the server) provides resources or services, while other nodes (clients) request access to them. A phrasing for the interview: > **Client-server is an architecture where the server acts as the central node providing services, and clients are the consumers of those services. Interaction follows a request → response pattern.** --- ## How it works (simple logic) 1. **The client sends a request** (for example, to open a web page). 2. **The server receives it, processes it**, and performs the needed actions. 3. **The server sends back a response** (an HTML page, a file, data). This is the **request → response** model. --- ## Examples of client-server services ### 1. Web services - a browser (client) - a web server (Nginx, Apache) ### 2. Mail systems - Outlook, Thunderbird → an SMTP/IMAP server ### 3. File services - an SMB client → a file server ### 4. Databases - an application → a DBMS (PostgreSQL, MySQL, MSSQL) ### 5. Domain services - a workstation → an AD Domain Controller --- ## Roles in a client-server network ### Client - initiates the request - waits for a response - does not store shared resources - can be a PC, a browser, an application, a mobile device ### Server - always "online" - stores resources and manages them - handles many requests - has increased performance --- ## Main characteristics of the client-server model #### 1. Centralization Resources are located in one place - on the server. This simplifies: - management - security - backups - scaling --- #### 2. Separation of roles Client ≠ server. The client does not share its own resources but consumes the server's. --- #### 3. Easy to scale You can: - add servers, - balance load, - offload services by role (a DB server, a web server, a file server). --- #### 4. Increased security Through the server you can: - control access - filter requests - keep logs - apply policies --- ## Comparison with P2P (Peer-to-Peer) | Criterion | Client-server | P2P | |---|---|---| | Center | There is a server | None, all peers are equal | | Reliability | High (depends on the server) | Depends on the nodes | | Scaling | Excellent | Limited | | Example | Internet sites | Torrent networks | --- ## Where the client-server model is used Practically **everywhere**: - the internet - corporate networks - cloud services - authorization systems - games with a central server --- ## Ready answer for the interview > **A client-server network is an architecture where the server provides services or resources, and clients request access to them.** > **Interaction follows the request-response model.** > **The server is a centralized, always-available node that handles many client requests; the client is the consumer of the service.** > **Examples: web servers, file servers, databases, domain services.** --- ## Cheat sheet (5 seconds before the interview) - Client-server = request → response. - The server serves, the client consumes. - Centralization, management, security. - The main model of the internet and corporate networks. - Contrasted with P2P.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.