vertical-slices

Reduce cross-module coupling by dividing your TypeScript project into vertical slices, where each feature independently owns its contract, business rules, persistence logic, and tests.

The vertical slices pattern structures software projects as independent feature slices that own their contract, business rules, persistence, and tests, keeping business behavior out of transport or framework code.

Refactor to vertical slices by documenting a clear slice boundary and creating a compact design spec before implementation, ensuring each slice owns its business behavior and co-located persistence.

Yes, the vertical slices approach scales across both backend and fullstack TypeScript projects, enforcing explicit boundary contracts and dedicated test maturity gates for new features or refactoring.

Avoid vertical slices if your project cannot enforce explicit boundary contracts or co-located persistence, as the pattern relies on strict repository rules and feature-first folder structures to reduce coupling.

Structure feature-first folders with thin entrypoints that keep business behavior inside the vertical slice, enforcing explicit boundary contracts and co-located persistence rather than placing logic in transport code.