Stop Using UserService Blindly – Replace Entity-Based Layers with Intentional Design

Reducing Complexity: Replacing Entity-Based Services and Repositories with Purposeful Layers in Software Design

Developer Artyom Kornilov argues that mindless application of UserService/UserRepository patterns deforms software architecture over time.

Why This Matters

Key Insights

• • Services degrade into mere delegates when they only forward calls like userRepository.save(user)—adding cognitive load without isolating complexity.
• • Repositories become thin ORM wrappers when they lack complex data access logic—introducing file clutter while hiding nothing.
• • Ceremonial interfaces appear when multiple implementations are never needed—forcing navigation between contract and single implementation.
• • Over-abstraction driven by fear of under‑engineering leads to horizontal expansion of layers instead of meaningful vertical depth per component.

Practical Applications

• • Delegating Service: A UserService forwarding every call to UserRepository adds indirection – eliminate it unless orchestrating cross‑cutting concerns.
• • ORM Wrapper Repository: A UserRepository directly mapping JPA methods increases file count – remove it unless hiding sharding or caching complexity.
• • Layer‑per‑Entity: Creating OrderService, PaymentService per entity scatters related logic – replace with action‑based classes like ProcessPayment.
• • Junior Replication: New team members copy existing patterns out of familiarity – educate them on evaluating each layer’s purpose before adding noise.

References:

• https://dev.to/kornilovconstru/reducing-complexity-replacing-entity-based-services-and-repositories-with-purposeful-layers-in-3ike