liveBook · Manning

Backend

A backend is a software component or system that provides underlying processing, data, execution, or service functionality to other components.

How 5 Manning books explain it

Spring Start Here, Second Edition

The execution environment where backend software runs and processes client requests.

How it is used
Processes client requests, manages data, and returns responses in web and other server-side applications.
How deep it goes
Defines the server-side role and contrasts response styles, while leaving implementation details to later Spring discussions.
Examples
Uses online banking, prepared HTML responses, and raw JSON or XML responses as examples.
What you can do after
Understand how a backend processes client requests and responds in a web app.

Read how Spring Start Here, Second Edition explains backend →

Rust Servers, Services, and Apps

A backend service is a server-side application component that implements application functionality and exposes it to clients or other services.

How it is used
Places server-side application logic between client frontends and distributed infrastructure through exposed APIs.
How deep it goes
Defines responsibilities, requirements, integrations, and deployment forms but stops short of implementation details.
Examples
Uses a social media application's distributed stack and process- or container-based backend deployments.
What you can do after
Evaluate backend designs against API quality, throughput, latency, availability, and resource-footprint requirements.

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

Deep Learning with Python, Third Edition

The underlying execution framework that a machine-learning library can target to run models.

How it is used
Runs Keras models through a selectable tensor-computing framework and connects them to hardware and deployment ecosystems.
How deep it goes
Explains backend selection, portability, tensor operations, and gradients, while stopping short of framework-specific implementation details.
Examples
Uses KERAS_BACKEND, ~/.keras/keras.json, JAX selection, and NumPy’s prediction-only limitation as concrete examples.
What you can do after
Operate/configure Keras by selecting a backend before import and matching it to debugging, training, or inference needs.

Read how Deep Learning with Python, Third Edition explains backend →

Building User-Friendly DSLs

The server-side part of a software system that provides services, storage, and processing for its frontend.

How it is used
Supports a Domain IDE by exposing an API, storing DSL content, and enabling frontend persistence and Runtime generation.
How deep it goes
Implements a deliberately simple REST backend with JSON-file persistence, serialization, deserialization, and reference handling.
Examples
Uses a JSON file on disk with GET retrieval, PUT replacement, and AST reconstruction through deserialization.
What you can do after
Build a simple REST backend that persists, transports, and reconstructs an AST for a frontend client.

Read how Building User-Friendly DSLs explains backend →

Deep Learning with R, Third Edition

A backend engine is a software system that executes the numerical and machine-learning operations required by a higher-level framework.

How it is used
Runs Keras models by supplying low-level tensor computation, gradients, and hardware execution beneath its high-level API.
How deep it goes
Defines backend responsibilities and switching, then gives R configuration paths; stops short of implementing tensor operations or gradient internals.
Examples
Uses JAX selection in R, CPU/GPU backend suffixes, and workflows split across debugging, training, and inference.
What you can do after
Operate/configure Keras by selecting a backend with use_backend() or KERAS_BACKEND before loading keras3.

Read how Deep Learning with R, Third Edition explains backend →

Also covered in

What to know first

Related concepts

Questions about backend

What is backend?

A backend is a software component or system that provides underlying processing, data, execution, or service functionality to other components.

Which Manning books explain backend?

Spring Start Here, Second Edition, Rust Servers, Services, and Apps, Deep Learning with Python, Third Edition, Building User-Friendly DSLs and Deep Learning with R, Third Edition.

What should I know before learning backend?

Manning books that teach backend usually introduce contract, web application, HTML and language model first.

What is the difference between backend and frontend development?

A backend is a software component or system that provides underlying processing, data, execution, or service functionality to other components. Frontend development is the practice of building the user-facing, client-side interface and behavior through which people interact with software.

What kinds of backend are there?

Kinds of backend include JAX.

What is backend part of?

Backend is part of web application. A web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.

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.