Hello, dear friends. In this video, we will examine design patterns. So, let's begin. Software design patterns are common solutions to problems which are regularly encountered in programming. These particular patterns deal with object-oriented programming exclusively. So, applying these patterns to, say a functional environment is a thoroughly bad idea. Some pattern proponents even go so far as to say that in the object-oriented world these design patterns are full fledged to best practices. Though I often stop short of such an assertion. The patterns I'll be describing in this series originate from a book titled appropriately enough, "Design Patterns: Elements of Reusable Object-Oriented Software", written by a group of authors who have come to be known as the Gang of Four, as GoF. 

Some of the benefits of using design patterns are: design patterns are already defined and provides industry standard approach to solve a recurring problem, so it saves time if we sensibly use the design pattern. There are many Java design patterns that we can use in our Java-based projects. Using design patterns promotes reusability that leads to more robust and highly maintainable code. It helps in reducing total cost of ownership. TCO of the software product. Since design patterns are already defined, it makes our code easy to understand and debug. 

It leads to faster development and new members of team understand it easily. According to GoF, design patterns are classified in three groups: creational, structural, behavioral. For example, abstract factory singleton or prototype are creational design patterns. Adapter, composite, or facade are structural patterns. And observer, iterator, and visitor patterns are behavioral patterns. In the following videos, we will start examining design patterns by implementing Java projects. In the next video, we will start by looking into the singleton design pattern. See you in the next video.