Layer-based (controller/service/repository) or feature-based (invoice…

Dhruv Joshi

Software Developer | Java, Spring Boot, React | Learning system design one outage at a time

7 Oct 2026 Java & Spring Developers India

Layer-based (controller/service/repository) or feature-based (invoice/, payment/, customer/)? Our codebase is layer-based and finding things is getting hard at ~200 classes.

8 reactions2 comments

Comments

RM
Rohan Malhotra8 Oct 2026
Feature-based once you pass ~50 classes. Each feature package has its own controller/service/repo. Package-private by default.
AS
Aarav Sharma8 Oct 2026
+1 to feature-based. Bonus: it makes extracting a module later much easier.

Join the conversation

Join workOwon to react, comment and follow people and communities you care about.

Layer-based (controller/service/repository) or feature-based (invoice/, payment/, customer/)? Our codebase…

Comments

Layer-based (controller/service/repository) or feature-based (invoice/, payment/, customer/)? Our codebase…

Comments