-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Persistence Best Practices for Java Applications
By :

Layers, layers, and more layers – sometimes, they’re excellent allies helping split responsibility, reducing and centralizing the development error risks, and facilitating the adoption of the single responsibility principle from SOLID. Eventually, too many layers can become counterproductive and increase the code design’s complexity. When should a new layer be added or removed? The answer will be hidden under each individual application’s contextual challenges, technical needs, and business needs.
Through a journey highlighted with code demonstrations, we explored several patterns, from the unstructured and zero-layer application design to the multiple types of multi-tier design adoption and business-oriented simplification techniques. On this journey, we learned about the benefits and drawbacks of using layers to abstract the database from the client in a software application.
Furthermore, we explicitly stated that there is more to the persistence...