Service
A service is a software or computing capability that provides defined functionality to users or other components through an interaction boundary.
Pro Angular 16
An Angular service is a class that provides reusable application functionality and can be supplied through dependency injection.
- How it is used
- Supplies shared functionality without requiring parent components to distribute objects through input properties.
- How deep it goes
- Works through decoration, module registration, constructor injection, and a service-to-service dependency chain.
- Examples
- Uses a shared discount editor and display, then applies services to a shopping cart and server-platform check.
- What you can do after
- Build it from scratch by registering a decorated class and injecting it into components or other services.
ASP.NET Core in Action, 3e
A service is a class that provides a discrete piece of functionality to an application and can be registered with its dependency-injection container.
- How it is used
- Supplies modular application functionality and lets Razor Page handlers delegate business logic.
- How deep it goes
- Defines services, demonstrates registration and endpoint injection, and explains instance reuse through three lifetimes.
- Examples
- Uses e-commerce calculators and Razor Pages registration to illustrate service composition and setup.
- What you can do after
- Operate/configure it through `WebApplicationBuilder.Services`, request it in handlers, and choose a lifetime for its instances.
Simple Object-Oriented Design: Create clean, maintainable applications
A service is a component that encapsulates business rules involving one or more domain entities.
- How it is used
- Coordinates backend business actions whose rules span entities or require external information.
- How deep it goes
- Explains service extraction through consistency rationale, validation coordination, tradeoffs, and a worked registration implementation.
- Examples
- Demonstrates employee registration for an offering with repositories, a validator, and business-rule failures.
- What you can do after
- Apply it via a service class to enforce cross-entity business rules before mutating an entity.
Read how Simple Object-Oriented Design: Create clean, maintainable applications explains service →
Data Pipelines with Apache Airflow, Second Edition
An external system is a software or computing system outside Airflow that participates in an integrated workload or data operation.
- How it is used
- Connects Airflow tasks to external systems and orchestrates data movement, queries, and computation across them.
- How deep it goes
- Explains operator abstraction, provider installation, workload offloading, and testing trade-offs, but does not detail each service's internals.
- Examples
- Uses S3 object copying, cloud-provider operators, PostgreSQL-backed DAG tests, and external Spark or database processing.
- What you can do after
- Operate/configure Airflow integrations through provider operators and choose between mocking, emulating, or directly using external services.
Read how Data Pipelines with Apache Airflow, Second Edition explains service →
Platform Engineering on Kubernetes
A service is an independently deployable software component that provides a bounded set of functionality within a distributed application.
- How it is used
- Frames distributed application design around independently evolving and differently scalable functionality.
- How deep it goes
- Compares monoliths with distributed services, stopping short of implementation interfaces, deployment mechanics, and failure handling.
- Examples
- Uses a monolith-versus-distributed comparison and cloud-provider service categories, including managed PostgreSQL.
- What you can do after
- Evaluate distributed services against monoliths by comparing team autonomy, scaling scope, and coordination costs.
Read how Platform Engineering on Kubernetes explains service →
Elixir in Action, Third Edition
A service is a part of a system that runs in a separate operating-system process.
- How it is used
- Frames separate processes as units for fault tolerance, scalability, state ownership, and interprocess communication.
- How deep it goes
- Defines services mechanically, compares them with microservices, and explains process boundaries, communication modes, and trade-offs.
- Examples
- Uses an online multiplayer game and a to-do system with list servers, a cache, a database process, and worker pools.
- What you can do after
- Evaluate service boundaries and choose calls or casts according to response guarantees, responsiveness, consistency, and back pressure.
Functional Design and Architecture: Examples in Haskell
A software service is a separately organized component that provides functionality through a defined interaction boundary.
- How it is used
- Decouples subsystems and clarifies architectural boundaries while keeping implementation details behind functional interfaces.
- How deep it goes
- Defines functional services, compares implementation patterns, and stops short of treating them as whole-architecture patterns.
- Examples
- Uses Hdl and Device layers, hardware-subsystem decomposition, Service Handles, mocks, and fakes as concrete design examples.
- What you can do after
- Apply functional interfaces to isolate subsystems, substitute implementations, and test business logic independently from external systems.
Read how Functional Design and Architecture: Examples in Haskell explains service →
Related concepts
- notifications serviceincludes · A notifications service is software that creates and delivers messages informing users or other systems about specified events or completed operations through communication channels.
- contractequivalent to · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- microservice architecturepart of · Microservice architecture is a software architectural style that organizes an application as independently deployable services with focused responsibilities that communicate through defined interfaces.
- scalabilityuses · Scalability is the ability of a system, process, or method to accommodate increasing workload, size, or demand while maintaining acceptable operation.
- distributed systempart of · A distributed system is a computing system whose components run across multiple networked processes or machines and coordinate through communication.
- HTTPuses · HTTP is a standardized application-layer protocol that defines request-and-response messages for transferring resource representations between networked systems.
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.