design-patterns

Vertical-slice architecture in Spring Boot organizes feature development by splitting code into cohesive modules with thin controllers, dedicated services, and repository-first data access. It enforces separation of concerns and standardized domain exceptions for each feature.

Structure your new Kotlin feature by creating a strict vertical-slice module containing thin controllers, cohesive services, repository-first data access layers, dedicated models, and standardized domain exceptions. Cross-feature dependencies should be handled through repositories.

Vertical-slice architecture works for large Spring Boot applications by enforcing a consistent folder structure and standardized patterns across feature teams. It ensures clear responsibilities and separation of concerns across all new modules.

The best way to handle cross-feature dependencies in a vertical-slice architecture is through repository-first data access. This approach encourages features to interact via repositories rather than direct service calls, maintaining strict separation of concerns.

Vertical-slice architecture may not suit your Spring Boot project if your features lack clear domain boundaries or if you cannot enforce a strict folder structure. It requires standardized Controller, Service, Repository, Model, and Exception patterns for every new feature.