Should the Service Layer Use Interfaces? A Critical Discussion

Reasons Not to Use Interfaces

The author lists three typical reasons for adding interfaces to Service and DAO layers—enabling top‑down coding before implementation, supporting Spring AOP dynamic proxies, and allowing multiple implementations—then argues that each of these reasons is flawed. Without interfaces, developers can still code top‑down by creating placeholder methods, Spring can use CGLIB instead of JDK proxies, and multiple implementations are rarely needed.

Project Structure and Interface Implementation

The article describes common layer‑based project structures (Controller → Service → Dao) and shows how interfaces are usually placed in a separate package. It then explores two approaches for handling multiple Service implementations: adding new implementation packages under the same interface or creating a separate Service module, highlighting the trade‑offs of each method.

Disadvantages of Not Using Interfaces

While omitting interfaces reduces boilerplate, the author notes that it hampers strong contract enforcement and IDE assistance when multiple implementations are required, making code less elegant and harder to maintain.

Conclusion

The article concludes that interfaces are unnecessary for most projects unless multiple Service implementations are anticipated; otherwise, a simpler structure without interfaces suffices.