Vertical slice
A vertical slice is an architectural partition that groups the functionality needed for an end-to-end feature or capability across the relevant system layers.
Claude at Work
A vertical slice is an end-to-end implementation that crosses the application's layers or components to deliver a complete feature path.
- How it is used
- Organizes an end-to-end messaging feature into small, demonstrable deliveries that can be reviewed and steered.
- How deep it goes
- Develops a delivery sequence and per-slice protocol, including scenario approval, failing tests, implementation, and exit criteria.
- Examples
- Uses channel creation, message history, and real-time delivery as successive messaging slices with demonstrable outcomes.
- What you can do after
- Evaluate and plan reviewable feature slices, with behavior scenarios and explicit approval before implementation.
Microservices Patterns, Second Edition
A vertical slice is an architectural partition that cuts through multiple layers to contain the functionality for a specific business capability.
- How it is used
- Partitions a modular monolith by subdomain, keeping business logic and supporting web/API and infrastructure logic together.
- How deep it goes
- Defines the module and names its adapters and design decisions, while deferring build-project organization.
- Examples
- Uses a Consumer module with REST API, domain, and infrastructure packages.
- What you can do after
- Build it from scratch by grouping a subdomain’s business logic and supporting adapters in an owned module.
Read how Microservices Patterns, Second Edition explains vertical slice →
Also covered in
- F# in Action: A Revised Edition of Get Programming with F#
- Grokking Software ArchitectureIn early access (MEAP)
- Clean Applications with Hexagonal ArchitectureIn early access (MEAP)
What to know first
- cross-cutting concernA cross-cutting concern is a software responsibility or behavior that affects multiple components, features, or architectural layers rather than belonging to one alone.
Related concepts
- delivery planused by · A delivery plan is a staged plan that organizes work into manageable increments for producing and reviewing a deliverable.
- modular monolithimplements · A modular monolith is an application deployed as a single unit and internally organized into distinct modules with defined boundaries and controlled dependencies.
- layered architecturealternative to · Layered architecture is a software organization pattern that separates responsibilities into ordered layers with defined roles and constrained dependencies, typically from higher-level layers to lower-level ones.
- n-tier architecturealternative to · N-tier architecture organizes an application into distinct tiers with separate responsibilities and defined interactions, which may be logical divisions or separately deployed components.
Questions about vertical slice
What is vertical slice?
A vertical slice is an architectural partition that groups the functionality needed for an end-to-end feature or capability across the relevant system layers.
Which Manning books explain vertical slice?
Claude at Work and Microservices Patterns, Second Edition.
What should I know before learning vertical slice?
Manning books that teach vertical slice usually introduce cross-cutting concern first.
What is the difference between vertical slice and clean architecture?
A vertical slice is an architectural partition that groups the functionality needed for an end-to-end feature or capability across the relevant system layers. Clean Architecture is a software architecture pattern that isolates stable business rules from external frameworks, interfaces, and infrastructure through inward-directed dependencies.
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.

