Client-server architecture
A distributed computing pattern in which clients request services or resources from servers, which process the requests and provide results.
Building Web APIs with ASP.NET Core
The client-server approach separates client user-interface concerns from server-side data and application concerns.
- How it is used
- Separates client user-interface concerns from web API data concerns as a REST constraint.
- How deep it goes
- Defines the separation and applies it to HTTP responses and CORS configuration, without detailing client or server internals.
- Examples
- Uses controllers, Minimal APIs, and ASP.NET Core CORS policies to show how independent clients reach an API.
- What you can do after
- Operate/configure client access to an ASP.NET Core API with CORS middleware or endpoint policies while keeping responses client-independent.
Read how Building Web APIs with ASP.NET Core explains client-server architecture →
Acing the CCNA Exam: Volume 2 Advanced Networking and Security
Client-server architecture is a distributed-system pattern that separates clients requesting services from servers providing them.
- How it is used
- Deploys a reusable pattern for DHCP services, file transfer, and REST APIs.
- How deep it goes
- Defines roles, request flow, statefulness, and examples, but leaves implementation details to each protocol.
- Examples
- Uses DHCP DORA exchanges, Cisco IOS DHCP pools, REST requests, and TFTP transfers between PCs and network devices.
- What you can do after
- Apply it to recognize service roles, trace request flows, and configure basic Cisco IOS DHCP behavior.
Building User-Friendly DSLs
A software architecture in which clients request services or data from a server that provides them.
- How it is used
- Deploys centralized synchronization for real-time collaborative editing across multiple devices.
- How deep it goes
- Explains client updates, server broadcasting, latency conflicts, rollback, and first-arrival resolution, while deferring CRDT-based conflict prevention.
- Examples
- Uses shared document editing, keystroke-sized changes, rollback, and structured property-update records.
- What you can do after
- Evaluate/understand centralized synchronization and first-arrival conflict handling in collaborative editing.
Read how Building User-Friendly DSLs explains client-server architecture →
Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more
A client-server application is software organized into clients that request services from a separate server process.
- How it is used
- Contrasts daemon-mediated container execution with direct fork/exec execution to clarify process ownership, complexity, and auditing.
- How deep it goes
- Traces client, daemon, containerd, OCI runtime, process ancestry, and loginuid effects, but stops short of daemon implementation internals.
- Examples
- Uses architecture diagrams, container process inspection, loginuid output, and audit records for host-file modification.
- What you can do after
- Diagnose process ancestry and user attribution by inspecting container PIDs, loginuid values, and audit records.
Rust Servers, Services, and Apps
The client-server model is a computing architecture in which clients request data or computation from dedicated servers that manage resources.
- How it is used
- Structures web services and distributed systems by separating resource requests from centralized data and computation management.
- How deep it goes
- Defines roles, authorization, REST constraints, and request methods, but stops short of implementation internals.
- Examples
- Uses web browsers, web servers, REST resources, HTTP-style methods, and weather, course, user, and shipment APIs.
- What you can do after
- Evaluate request flows by identifying client responsibilities, server responsibilities, authorization, resources, and state-changing operations.
Read how Rust Servers, Services, and Apps explains client-server architecture →
Related concepts
- RESTused by · REST is an architectural style for distributed hypermedia systems that organizes interactions around resources and representations through constraints including a uniform interface, stateless communication, cacheability, and layered components.
- MCPused by · The Model Context Protocol is an open standard protocol that defines how AI applications connect with external tools, data sources, and other contextual resources.
- dhcpused by · The Dynamic Host Configuration Protocol (DHCP) is a network protocol that automatically assigns devices IP addresses and related configuration information.
- peer-to-peer networkcontrasts with · A peer-to-peer network is a distributed architecture in which equivalent participants communicate and exchange resources directly without a central intermediary.
- Dockerused by · Docker is a platform and ecosystem for building, distributing, and running applications in containers.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.