Spring 5 Design Patterns

The best approach to designing your data-access

In previous chapters, you have seen that one of Spring's goals is to allow you to develop applications by following one of the OOPs principles of coding to interfaces. Any enterprise application needs to read data and write data to any kind of database, and to meet this requirement, we have to write the persistence logic. Spring allows you to avoid the scattering of persistence logic across all the modules in your application. For this, we can create a different component for data access and persistence logic, and this component is known as a data access object (DAO). Let's see, in the following diagram, the best approach to create modules in layered applications:

As you can see in the preceding ...