liveBook · Manning

Server

A server is a computer system or software process that provides data, resources, or services to other systems, typically by responding to requests.

How 14 Manning books explain it

Learn Go with Pocket-Sized Projects

An HTTP server is software that accepts HTTP requests and returns responses over the HTTP protocol.

How it is used
Uses HTTP servers to expose a game API and provide a browser interface to a habits service.
How deep it goes
Builds listeners, routers and handlers, with error handling and tests; leaves containerization and deployment outside scope.
Examples
Implements a game API and a habits interface, plus a minimal root handler returning a greeting.
What you can do after
Apply it via Go's net/http to start a listener, route requests, write responses and test handlers.

Read how Learn Go with Pocket-Sized Projects explains server →

Rust Servers, Services, and Apps

A web server is software that accepts network requests and returns responses, typically over HTTP.

How it is used
Serves static pages and JSON data, then hosts routed APIs and frontend form requests.
How deep it goes
Builds a limited GET server from TCP and HTTP components, then configures an Actix server; stops short of a production-ready implementation.
Examples
Tests HTML, CSS, JSON, and invalid paths with a browser or curl, and builds an Actix /health endpoint.
What you can do after
Build it from scratch with Rust’s standard library or operate/configure it with Actix routes, handlers, and HttpServer.

Read how Rust Servers, Services, and Apps explains server →

The Well-Grounded Python Developer: How the pros use Python and Flask

Server software is software that provides network-accessible functionality and enables a computer to act as a server.

How it is used
Provides network-accessible functionality for a web application while centralizing its features and updates.
How deep it goes
Defines server software, traces browser request-response behavior, and runs a local Flask example; leaves HTTP protocol details beyond scope.
Examples
Uses a Flask Hello World route and a browser request to localhost to show a server receiving and answering requests.
What you can do after
Operate/configure it: run the Flask development server locally and recognize why it should not serve a public production application.

Read how The Well-Grounded Python Developer: How the pros use Python and Flask explains server →

ASP.NET Core in Action, 3e

A web server is software or a host system that receives HTTP requests and returns HTTP responses containing web resources.

How it is used
Frames the server as the entry point that receives browser requests and returns application-generated HTTP responses.
How deep it goes
Explains HTTP request and response parts, Kestrel hosting, HttpContext construction, and reverse-proxy placement without detailing implementation internals.
Examples
Uses browser page requests, generated HTML, access-denied responses, Kestrel hosting, and IIS or NGINX reverse-proxy deployments.
What you can do after
Evaluate request flow by distinguishing client requests, server processing, application responses, and reverse-proxy forwarding.

Read how ASP.NET Core in Action, 3e explains server →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

A web server is software that receives and responds to requests for web resources or application content.

How it is used
Uses web servers to handle customer requests in web shops and expose an image-processing REST API.
How deep it goes
Walks through Apache setup and shows Express routes, without requiring an in-depth understanding of Express.
Examples
Demonstrates an Apache default website, a web shop, and an Express image-processing API.
What you can do after
Operate/configure it on EC2 by installing and starting Apache, allowing HTTP traffic, and checking the site in a browser.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains server →

Grokking Software Architecture

A server is a software component that receives client requests, performs the requested processing, and returns responses.

How it is used
Explains the server as the doer in a client-server system, responsible for fulfilling requests under an API contract.
How deep it goes
Defines server duties and walks through request-response steps, client workload tradeoffs, and immutable-server rationale.
Examples
Uses a burger order and a GET /user/123 request to illustrate server processing and responses.
What you can do after
Evaluate and understand server responsibilities, client-server workload choices, and the consequences of crossing a network boundary.

Read how Grokking Software Architecture explains server →

Go in Practice, Second Edition

A web server is software that listens for network requests and returns responses over web protocols such as HTTP.

How it is used
Serves browser and API requests directly from a Go application.
How deep it goes
Works through a runnable listener and handler, then identifies routing, middleware, startup, shutdown, and production planning without detailing their implementations here.
Examples
Uses a localhost greeting server and a media-upload API that stores files and queues transcoding jobs.
What you can do after
Build it from scratch with Go's net/http, registering a path handler and starting a localhost listener.

Read how Go in Practice, Second Edition explains server →

Grokking Concurrency

A server application is a program that listens for client connections and provides services over those connections.

How it is used
Uses servers to introduce client communication and motivate concurrent handling, then coordinates worker processes in a map-and-reduce application.
How deep it goes
Explains socket binding, accepting connections, and message exchange through a basic implementation, then identifies its sequential handling limitation.
Examples
Uses a pizza-ordering service tested with Netcat and a map-and-reduce program that assigns files to workers.
What you can do after
Builds a basic socket server and tests its request-response behavior with Netcat.

Read how Grokking Concurrency explains server →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

An HTTP server is software that listens for HTTP requests and returns HTTP responses.

How it is used
Builds a single microservice baseline before composing multiple services.
How deep it goes
Builds a runnable Express server with one route and local testing, while skimming broader Node.js and production concerns.
Examples
Uses Hello World, localhost:3000, and browser-based video playback through /video.
What you can do after
Build it from scratch with Node.js and Express, run it from a terminal, and validate it in a browser.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains server →

Think Like a CTO

A server is a computing system or software service that provides resources or functionality to other systems over a network.

How it is used
Supports organizational services as part of on-premises infrastructure.
How deep it goes
Explains hosting, capacity and physical operating needs, but not server installation procedures.
Examples
Uses an online promotion to show internal server capacity reassigned to frontline servers.
What you can do after
Evaluate/understand server capacity decisions using procurement lead times, hosting options and physical requirements.

Read how Think Like a CTO explains server →

Fundamentals of Cybersecurity

A server is a computing system or software process that provides services or resources to other systems over a network.

How it is used
Describes how networked computers provide resources and services to requesting clients.
How deep it goes
Defines servers, explains request and response roles, and lists service examples without detailing server implementation.
Examples
Uses web, file, email, and application servers as examples of services provided.
What you can do after
Understand how clients request services and resources from servers.

Read how Fundamentals of Cybersecurity explains server →

Go by Example

An HTTP server is software that accepts and processes Hypertext Transfer Protocol requests and returns responses.

How it is used
Builds runnable HTTP services and tests clients against controlled HTTP servers.
How deep it goes
Explains handler dispatch, response-writing order, concurrency, configuration, and testing, without detailing network internals.
Examples
Uses a health-check service, localhost:8080, curl output, and a test server counting concurrent client requests.
What you can do after
Build it from scratch by implementing handlers, configuring an address, launching a server, and testing its responses.

Read how Go by Example explains server →

Learn Rust in a Month of Lunches

A server is a program that listens for client requests and provides responses over a network.

How it is used
Builds a local web application and makes a word-guessing game accessible through browser requests.
How deep it goes
Explains routes, GET requests, localhost, ports, extractors, and serving, but stops short of a full Axum explanation.
Examples
Uses root, guessing-game, game-guess, and double-number routes with successful responses, parsing errors, and a 404 response.
What you can do after
Builds a small local server with Axum routes, asynchronous handlers, path extraction, and browser-visible responses.

Read how Learn Rust in a Month of Lunches explains server →

Vanilla Web

A networked system that responds to client requests by returning resources or providing services.

How it is used
Routes direct URL requests to the appropriate SPA shell, file, API response, or not-found response.
How deep it goes
Defines response rules for app routes, files, APIs, and missing routes, then contrasts SPA rewrites with route-specific HTML.
Examples
Uses /products/42, /assets/app.js, /api/products, and a /dashboard/ deployment path to illustrate routing decisions.
What you can do after
Configure rewrites that serve app routes without intercepting static assets, API endpoints, or unknown paths.

Read how Vanilla Web explains server →

Also covered in

What to know first

Related concepts

Questions about server

What is server?

A server is a computer system or software process that provides data, resources, or services to other systems, typically by responding to requests.

Which Manning books explain server?

Learn Go with Pocket-Sized Projects, Rust Servers, Services, and Apps, The Well-Grounded Python Developer: How the pros use Python and Flask, ASP.NET Core in Action, 3e, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, Grokking Software Architecture, Go in Practice, Second Edition, Grokking Concurrency and 6 more.

What should I know before learning server?

Manning books that teach server usually introduce HTTP, HTML, IP address and Python first.

What kinds of server are there?

Kinds of server include NGINX, Kafka broker, authoritative dns server and centralized DHCP server.

What is server part of?

Server is part of data center. A data center is a physical facility housing computing, storage, networking, and supporting infrastructure for operating information systems and digital services.

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.