Self-service
Self-service is a mode in which users independently obtain resources or perform supported tasks without requiring an intermediary for each request.
Effective Platform Engineering
Self-service is a pattern in which users obtain resources or perform supported operations directly without depending on an intermediary for each request.
- How it is used
- Enables development teams to obtain platform capabilities and complete delivery tasks without waiting for another team to fulfill each request.
- How deep it goes
- Develops API-first interfaces, team-based access, tool integration, and adoption measures; defers a complete identity-implementation comparison.
- Examples
- Uses instant team onboarding, a portal-based microservice deployment, and replacement of a ticketed process with a measured interface.
- What you can do after
- Build it from scratch as an API-backed platform capability, then evaluate it through task time, onboarding, and adoption.
Read how Effective Platform Engineering explains self-service →
Effective Data Analysis
Self-service analytics is a practice in which stakeholders independently explore, query, and interpret data using prepared analytical resources.
- How it is used
- Enables stakeholders to answer recurring questions independently while reducing routine demands on analytics teams.
- How deep it goes
- Lays out a strategy for identifying requests, selecting filters, testing tools, documenting results, and iterating.
- Examples
- Illustrates filtered product dashboards, pre-aggregated financial tables, and reports comparing purchase prices across locations.
- What you can do after
- Apply it by designing and improving shared analytical resources around stakeholder needs and feedback.
Effective Conversational AI
A service interaction in which customers complete a task or obtain information without assistance from a human agent.
- How it is used
- Enables customers to complete tasks through a virtual assistant rather than receive instructions or immediately use a human agent.
- How deep it goes
- Develops flow-design choices, backend shortcuts, progress cues, and escalation paths; leaves integration implementation unspecified.
- Examples
- Contrasts a balance answer with FAQ guidance, reorders an insurance claim response, and simplifies spoken member-ID collection.
- What you can do after
- Evaluate/understand it by checking task completion and opt-outs, then reducing avoidable questions while retaining alternatives and agent routes.
Read how Effective Conversational AI explains self-service →
First-Party Data Activation
Self-service is a capability that allows users to perform tasks independently without ongoing assistance from specialized technical teams.
- How it is used
- Reduces campaign bottlenecks by letting marketers design and activate audiences with less ongoing technical support.
- How deep it goes
- Describes audience-design features and solution evaluation criteria, while deferring detailed technical instructions.
- Examples
- Uses analytics-built audience dashboards and GrowthLoop segmentation to illustrate ways marketers can work independently.
- What you can do after
- Evaluate self-service solutions through use-case demonstrations or pilots involving less-technical marketers.
Read how First-Party Data Activation explains self-service →
Platform Engineering on Kubernetes
A self-service capability lets development teams provision, configure, or operate platform resources without direct intervention from platform engineers.
- How it is used
- Uses platform APIs to let development teams consume assembled cloud and operational capabilities independently.
- How deep it goes
- Defines self-service through platform APIs and team capabilities, but stops short of prescribing a single implementation.
- Examples
- Points to OpenShift and Tanzu as opinionated Kubernetes-based tools that can support out-of-the-box workflows.
- What you can do after
- Apply it via platform APIs to consume platform capabilities while reducing direct platform-engineer intervention.
Read how Platform Engineering on Kubernetes explains self-service →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
Self-service is an operational practice in which teams independently request, create, or modify resources without requiring another team to perform every change.
- How it is used
- Uses shared infrastructure modules to let application teams progress independently while preserving expert release review.
- How deep it goes
- Explains an approval workflow and a destructive-update failure, but stops short of specifying module standards or migration procedures.
- Examples
- Uses a Beans team PostgreSQL 12 upgrade that risks deleting an existing database.
- What you can do after
- Apply it via shared modules, staged approval, and specialist review for potentially disruptive infrastructure changes.
Also covered in
- Architecture Modernization: Socio-technical alignment of software, strategy, and structure
- Architecting an Apache Iceberg Lakehouse
What to know first
- analystAn analyst is a professional who examines and interprets information, data, or organizational needs to produce findings, requirements, or recommendations that support decisions.
- authenticationAuthentication is the process of verifying the claimed identity of a user, service, device, or other entity.
- data warehouseA data warehouse is a repository that integrates and organizes data for analytical querying, reporting, and analysis.
- cognitive loadCognitive load is the mental effort required to process information, retain it in working memory, or perform a task.
Related concepts
- deliverableuses · A deliverable is a defined work product, output, result, capability, or change that a project or team is expected to produce.
- internal developer platformused by · An internal developer platform is an organization-provided system of self-service interfaces, automation, abstractions, and reusable capabilities that supports software development and operation.
- opt-out requestaddresses · An opt-out request expresses a person's decision not to participate in, receive, or permit a specified activity.
- platform engineeringused by · Platform engineering is the discipline of designing and operating internal platforms that provide software teams with reusable capabilities and self-service workflows.
- API-first approachproduced by · An API-first approach treats APIs as primary interfaces or products by defining their contracts before or independently of the implementations and consumers that rely on them.
- cognitive loadaddresses · Cognitive load is the mental effort required to process information, retain it in working memory, or perform a task.
Questions about self-service
What is self-service?
Self-service is a mode in which users independently obtain resources or perform supported tasks without requiring an intermediary for each request.
Which Manning books explain self-service?
Effective Platform Engineering, Effective Data Analysis, Effective Conversational AI, First-Party Data Activation, Platform Engineering on Kubernetes and Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform.
What should I know before learning self-service?
Manning books that teach self-service usually introduce analyst, authentication, data warehouse and cognitive load first.
What is self-service also called?
Self-service is also called self-serve.
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.





