Book Image

Spring 5 Design Patterns

By : Dinesh Rajput
Book Image

Spring 5 Design Patterns

By: Dinesh Rajput

Overview of this book

Design patterns help speed up the development process by offering well tested and proven solutions to common problems. These patterns coupled with the Spring framework offer tremendous improvements in the development process. The book begins with an overview of Spring Framework 5.0 and design patterns. You will understand the Dependency Injection pattern, which is the main principle behind the decoupling process that Spring performs, thus making it easier to manage your code. You will learn how GoF patterns can be used in Application Design. You will then learn to use Proxy patterns in Aspect Oriented Programming and remoting. Moving on, you will understand the JDBC template patterns and their use in abstracting database access. Then, you will be introduced to MVC patterns to build Reactive web applications. Finally, you will move on to more advanced topics such as Reactive streams and Concurrency. At the end of this book, you will be well equipped to develop efficient enterprise applications using Spring 5 with common design patterns
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface

The data access object pattern


The data access object (DAO) pattern is a very popular design pattern for the persistent layer in a J2EE application. It separates the business logic layer and persistence layer. The DAO pattern is based on the encapsulation and abstraction object-oriented principles. The context for using the DAO pattern is to access and persist data depending on the underlying vendor implementation and type of storage, such as object-oriented database, flat files, relational databases, and so on. Using the DAO pattern, you can create a DAO interface, and implement this DAO interface to abstract and encapsulate all access to the data source. This DAO implementation manages the database's resources like connections with the data source.

The DAO interfaces are very generic to all the underlying data source mechanisms, and don't need to change for any changes in the low-level persistence technologies. This pattern allows you to adopt any different data access technologies without...