Backend

As explained in 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.

A backend service is a server-side application component that applies business rules, accesses databases, performs computation-heavy work, integrates with other services, and exposes functionality through APIs. Application frontends use these services to complete tasks for users. section 1.1

Backend services are shaped by several operational and architectural requirements:

• Well-designed APIs reduce unnecessary roundtrips between clients and services. section 1.2
• High throughput, short response times, predictable latency, and availability support varying application loads. section 1.2
• Services may run as individual processes on physical or virtual machines, or as containerized microservices managed by orchestration environments. section 1.1
• Backends interact with infrastructure such as databases, key/value stores, caches, messaging systems, load balancers, proxies, and service discovery platforms. section 1.1

Social media application stack

A social media application can place frontend clients above backend services, with distributed infrastructure supporting communication, persistence, operations, security, and monitoring. section 1.1

Figure 1.1 A simplified distributed systems stack for a social media application

Use the distributed-stack figure to trace how frontends, backend services, and supporting infrastructure cooperate in a social media application. section 1.1

How Rust Servers, Services, and Apps covers it

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.

How it connects

Connects application frontends, APIs, databases, caching, messaging, service discovery, and distributed software infrastructure.

liveBookmanning.com

Read Rust Servers, Services, and Apps on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Deep Learning with Python, Third EditionThe underlying execution framework that a machine-learning library can target to run models.
• 

  liveBookmanning.com
  Building User-Friendly DSLsThe server-side part of a software system that provides services, storage, and processing for its frontend.
• 

  liveBookmanning.com
  Deep Learning with R, Third EditionA backend engine is a software system that executes the numerical and machine-learning operations required by a higher-level framework.

Compare how 4 books explain backend →

Related concepts

• web applicationpart of · A web application is software that provides functionality through web technologies and is accessed by users through a browser or other web client.
• databaseuses · A database is an organized collection of persistent data managed by software for storage, retrieval, querying, and modification.
• natural language interfaceused by · A natural language interface enables interaction with a system through human-language text or speech.
• frontend developmentcontrasts with · Frontend development is the practice of building the user-facing, client-side interfaces and behavior through which people interact with software.
• JAXincludes · JAX is a Python library for high-performance array-based numerical computing with composable transformations including automatic differentiation, compilation, vectorization, and parallelization.
• contractuses · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.

This explainer was generated by Manning's knowledge graph from the text of Rust Servers, Services, and Apps. The section links point to the parts of the book it draws on.