Capability
A capability is an ability or permitted function that enables a person, organization, or system to perform an activity or achieve an outcome.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
A capability is an organizational ability to perform a business function or produce a business outcome.
- How it is used
- Frames decisions about domain boundaries, long-lived team ownership, and where modernization investment belongs.
- How deep it goes
- Develops the concept through mapping and organizational examples, without prescribing a fixed capability taxonomy or technical implementation.
- Examples
- Uses broadband self-fulfillment and cruise booking fulfillment to show capabilities informing boundaries and team organization.
- What you can do after
- Practice/perform capability mapping to propose boundaries, then evaluate them against team dependencies and investment priorities.
BDD in Action, Second Edition
A capability is an ability that enables users or stakeholders to achieve a goal or fulfill a task independently of a particular implementation.
- How it is used
- Connects business goals to the features selected to give users or stakeholders a useful ability.
- How deep it goes
- Defines an implementation-independent ability and traces it through feature discovery, examples, and specification organization without prescribing one implementation.
- Examples
- Uses commuter journey planning, disruption handling, frequent-flyer renewal, and a capability-organized feature-file tree.
- What you can do after
- Practice/perform capability discovery, select supporting features, and organize feature files around the abilities an application provides.
Read how BDD in Action, Second Edition explains capability →
The Design of Web APIs, Second Edition
An API capability is a function or set of functions that an API exposes to satisfy a user need.
- How it is used
- Guides API designers from user needs to versatile operations before programming-interface design begins.
- How deep it goes
- Explains an iterative Canvas process with paths, steps, inputs, outcomes, failures, and operations, stopping before interface syntax.
- Examples
- Uses social-network messaging, photo uploads, microwave cooking, car rental, delivery preferences, and account closure.
- What you can do after
- Build it from scratch by decomposing user needs, validating scope, and mapping steps to reusable operations.
Read how The Design of Web APIs, Second Edition explains capability →
Platform Engineering on Kubernetes
A platform capability is a platform-provided function that abstracts infrastructure or operational complexity behind a simpler developer-facing interface.
- How it is used
- Abstracts infrastructure concerns into shared APIs that application teams use while delivering distributed software.
- How deep it goes
- Explains API separation, team responsibilities, versioning, and environment consistency, but defers observability, metrics, logs, and service meshes.
- Examples
- Uses the Conference application, HTTP/gRPC interfaces, Dapr, shared infrastructure services, and feature flags as concrete examples.
- What you can do after
- Apply it via standard APIs to reduce application dependencies and consume infrastructure capabilities across environments.
Read how Platform Engineering on Kubernetes explains capability →
Effective Platform Engineering
A platform capability is a discrete function or service provided by an engineering platform to support software engineering work.
- How it is used
- Deploys reusable platform services to support multiple development teams instead of completing isolated infrastructure requests.
- How deep it goes
- Connects capabilities to discovery, qualification, cognitive-load measurement, observability, and platform pipelines, but defers detailed implementation.
- Examples
- Uses developer portals, centralized documentation, distributed tracing, service meshes, Kubernetes workloads, and domain-specific infrastructure pipelines.
- What you can do after
- Build and evaluate shared platform services by linking recurring developer problems to capabilities, expected effects, and implementation effort.
Read how Effective Platform Engineering explains capability →
Server-Side WebAssembly
A capability is an explicit, constrained authority that permits code to access a particular resource or operation.
- How it is used
- Controls how sandboxed Wasm components interact with host operating-system resources.
- How deep it goes
- Explains sandbox boundaries and demonstrates capability selection through WASI configuration, stopping short of a broader permission model.
- Examples
- Uses a greeting component that prints through WASI while disabling HTTP access.
- What you can do after
- Operate/configure Wasmtime and WASI hosts to grant standard output while withholding unused capabilities.
How Large Language Models Work
A capability is an ability or functional competence that a system can demonstrate.
- How it is used
- Frames LLM use around demonstrated abilities and reliability rather than broad claims about intelligence.
- How deep it goes
- Defines capability and surveys applications, while stopping short of detailed mechanisms or formal measurement.
- Examples
- Uses translation, transcription, document reading, search, and media generation as concrete capability examples.
- What you can do after
- Evaluate/understand LLM applications by separating what a model can produce from how reliably it produces it.
Read how How Large Language Models Work explains capability →
Related concepts
- performancecontrasts with · Performance is the measurable effectiveness or operational behavior of a system under specified conditions, assessed through relevant qualities such as task results, speed, responsiveness, throughput, or resource use.
- natural languageused by · Natural language is a human language that develops through social use and is used for communication, in spoken or written form.
- problem solvingincludes · Problem solving is the process of analyzing a problem and developing, selecting, or applying a solution to address it.
- quality characteristickind of · An aspect of a system's quality used to organize and evaluate testing risks.
- subdomainproduces · A subdomain is a bounded subdivision or subordinate namespace within a broader domain, such as a business area or a domain-name hierarchy.
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.