Builder Design Pattern
The builder design pattern is in many ways a continuation of the Abstract Factory design pattern. The builder enables us to create complex shapes split into steps and even merging more then one object with each other to create the outcome that we need. Most of the time you would start with a Factory, as it grows old move it into an Abstract Factory and only if at that stage it's logical to break it through into a builder you would move into a builder.
Singleton Design Pattern
- Delayed instantiation of an object. - A constant interface to gain access to the object. - Only one instance of the object is needed.
13:56
Factory Design Pattern
- When we need to have more control on customizing an item. - Removes the need for the implementing object to know how to implement. - Makes it easy to update and add more versions or updates of the
06:32
Abstract Factory Design Pattern
- When you need implementation of your factory to be more dynamic. - Only logical when it's expected to enable developers to extend functionality. - Avoid over complication when this usage is not n
10:04
Builder Design Pattern
- The jQuery $ method is a builder. - Multiple objects are needed. - Many steps are needed.
12:36
Builder Design Pattern Continued
- Fully integrating our builder into our Singleton. - See the builder in action. - Send you off to do some homework.
05:08
Prototype Design Pattern
- More efficient on memory to reuse methods. - Built in to the language capabilities. - Very easy to implement.
05:20