Skip to main content

Design Patterns

 Design pattern is a well know subject for most of the Software developers irrespective of Coding language (C#, Java, Python or JavaScript), but still most of the developers have difficulties working with patterns as they think them as complex code snippets. While most of them think of this a Solution Architect thing. Well yes Solution architects primarily job is to design well formed & working solution for any project, but Design patterns provides solution for so common problems that arises in code on daily basis that it's fundamental for every developer to learn them.

In this Series of Blog posts I will discuss Design patterns that are very general and are nice to have for a Junior developer as well:

Behavioral Design Patterns

  1. Strategy Design Pattern
  2. Singleton Design Pattern
  3. Command Design Pattern
  4. Null object Design Pattern
  5. Specification Design Pattern
  6. State Design Pattern
  7. Data access Design Pattern (Repository Design Pattern, Unit of Work)
  8. Mediator Design Pattern
  9. Observer Design Pattern
  10. Publish-Subscribe Design Pattern
  11. Chain of Responsibility Design Pattern
  12. Mediator Design Pattern
  13. Template Method Design Pattern
  14. Visitor Design Pattern

Creational Design Patterns 

  1. Builder Design Pattern
  2. Prototype Design Pattern

Structural Design Patterns

  1. Facade Design Pattern
  2. Decorator Design Pattern
  3. Composite Design Pattern
  4. Adapter Design Pattern
  5. Flyweight Design Pattern
  6. Proxy Design Pattern
Certainly there are 100 of other design patterns that are not listed here, but we will add more patterns to this list in near future.

Comments

Post a Comment

Popular posts from this blog

Design Patterns for better code - Null Object Design Pattern

Null being a part of programming languages is a billion dollar mistake. -Tony Hoare Writing everyday code irrespective of Language used (either be C# or Java or Python) we write null checks. Well we write null checks so often that a study estimates on an average one developer gives 5% of his entire development time to null checks only. So we can think of the importance of null checks. It's also the main problem of production issues specially for Junior developers.  Well writing null checks is not a problem until 100 lines of code contains 20 lines of null check code 😀 To reduce the number of lines for null checks, so that developer only focus on business logic instead of null check, Null Object design pattern was invented. Let's look at how we can use Null Object Design Pattern for our Invoice Application. Here we have different types of Invoice logic written in Separate Invoice classes (EmailInvoice, PDFInvoice, SMSInvoice). The User will choose the Invoice Type at runti...
Post a Comment
Read more