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

Best practices for configuring the DI pattern


The following are the best practices for configuring the DI pattern:

  • Configuration files should be separated categorically. Application beans should be separate from infrastructure beans. Currently, it's a bit difficult to follow.
  • Always specify the component name; never rely on generated names by the container.
  • It is a best practice to give a name along with a description of what the pattern does, where to apply it, and the problems it addresses.
  • The best practices for component scanning are as follows:
    • The components are scanned at startup, and it scans the JAR dependencies as well.
    • Bad practice: It scans all the packages of com and org. It increases the startup time of the application. Avoid such type of component scanning:
                @ComponenttScan (( {{ "org", "com" }} ))
    • Optimized: It scans only the specific packages as defined by us.
                 @ComponentScan ( {  
                  "com.packt.patterninspring.chapter4.
          ...