Modules vs Vertical Slices 2026: Macro vs Micro Architecture in the Modular Monolith

Q: Why is "Clean Architecture vs Vertical Slice Architecture" a category error and what is the right question to ask?

The framing presents the two as competing answers to the same question when they are non-competing answers to different questions at different scales. A module is a macro-architectural decision about where the business boundaries live, who owns the data, what public contract each module exposes, how modules communicate, and how the boundary is enforced — it answers "where does Billing end and Notifications begin". A vertical slice is a micro-architectural decision about how code for one feature is laid out inside one of those boundaries — it answers "where is everything for the create-ticket feature". The two operate on different axes: the macro axis is the system-decomposition concern (bounded contexts, contracts, data ownership, communication style), the micro axis is the feature-organisation concern (file layout, change locality, handler shape, internal style). The right question is two questions, asked at two scales, with two different answers. At the macro scale: where are the business boundaries, who owns the data, what contract does each module expose, how do modules communicate, and how is the boundary enforced. At the micro scale: what structure gives this module the most clarity given its shape — its feature count, its domain depth, its invariant density, its team size, its change cadence. The answers are independent: the macro decomposition is a system-wide decision the architecture team makes once and ratchets over time; the micro organisation is a per-module decision the module owner makes based on the module's shape. The team that conflates the two ends up either with a modular monolith that is a layered ball of mud with extra folders, or with a vertical slice architecture that has no boundaries to slice inside.

Satyam Kumar

Zurück zum Blog

microservices-patterns

Modules vs Vertical Slices: Macro vs Micro Architecture in the Modular Monolith (2026)

By Satyam KumarMay 19, 202633 min read

modular monolith vertical slice architecture clean architecture bounded contexts domain driven design cqrs mediator pattern software architecture module boundaries code organisation system design microservices migration archunit monorepo architectural patterns 2026

Modules vs Vertical Slices: Macro vs Micro Architecture in the Modular Monolith (2026)

Frequently Asked Questions

Artikel teilen

Twitter LinkedIn WhatsApp

Satyam Kumar

Founder & AI Architect, AppScale LLP

KI & Cloud Architekt. Ich helfe Teams, Systeme zu bauen, die auf Millionen skalieren.

LinkedIn GitHub

Modules vs Vertical Slices: Macro vs Micro Architecture in the Modular Monolith (2026)

Frequently Asked Questions

Artikel teilen

Comments

Leave a comment