Spring Design Patterns and Best Practices

Spring Design Patterns and Best Practices

English | MP4 | AVC 1920×1080 | AAC 48KHz 2ch | 7h 34m | 1.49 GB

Manage the Spring framework effectively to create your own system

This video will take you through Design Patterns and considerations required with the Spring framework. You will learn to use these design patterns to solve common problems when designing an application or system using the Spring Framework. This video will not only take you through ten of the essential GoF Design Patterns but also categories of patterns, considerations, and best practices required at different stages of Application Development.

Design Patterns help us write software that is flexible and future-proof. If you’re overusing if tests, you are probably not writing a well-designed object-oriented program. You will see how to use several design patterns, instead of if tests, to write a program where logic resides in an optimal location. The examples in this course use the command pattern, decorator pattern, visitor pattern, and several others.

You will understand the Dependency Injection pattern that is the main principle behind the decoupling process that Spring does, thus making it easier to manage your code. With practical examples, you will understand how patterns listed under the GoF patterns can be used in your Application Design. You will be introduced to the MVC pattern and how it treats controllers as Plain Old Java Objects, thus making it easier for testing the controllers. You will then learn about the Factory Method, and how it relates to one of the core components of object-oriented design: polymorphism.

This is a step-by-step approach which shows you the best way to use the Spring Framework to solve common problems when designing an application.

What You Will Learn

  • How to create a Spring project from the ground up
  • Why design patterns are important
  • Never call a constructor again! How to use the Factory pattern and Spring auto-wiring to create objects
  • Leverage the command pattern to future-proof software
  • Take advantage of Spring’s minimal-configuration deployment
  • Add behavior to existing compiled classes with Aspect Oriented Programming
  • Use Model-View-Controller to separate user interface, business logic, and data access logic
  • Consider how to leverage existing business and data logic with a different user interface