What's the difference between design patterns

Question

I'm new to Ruby on Rails, and I went through these articles.

• Design Patterns in Ruby: Observer, Singleton
• Design Patterns in Ruby

But I couldn't understand the actual difference between design patterns and design principles. Could someone please explain the distinction?

Answer 1

I think the answer from @ArslanAli is worth summarizing.

• Principles apply to all of programming. You should have a very good reason any time you choose not to follow principles.
• Patterns apply to specific, common problems. You should have a very good reason any time you choose to implement a pattern.

Answer 2

Design Principles:

Design principles are core abstract principles which we are supposed to follow while designing software. Remember they aren't concrete - rather abstract. They can be applied on any language, on any platform regardless of the state as long as we are within the permissible conditions.

Examples:

• Encapsulate what varies.
• Program to interfaces, not to implementations.
• Depend upon abstractions. Do not depend upon concrete classes.

Design Patterns:

They are solutions to real world problems that pop up time and again, so instead of reinventing the wheel, we follow the design patterns that are well-proven, tested by others, and safe to follow. Now, design patterns are specific; there are terms and conditions only in which a design pattern can be applied.

Examples:

• Singleton Pattern ( One class can only have one instance at a time )

• Adapter Pattern ( Match interface of different classes )

The following analogy will help you understand the difference better:

Principle: We should teach others in order to educate ourselves as well as others, and overall make our nation a progressive nation.

Pattern: In our country, each medical doctor graduate is supposed to teach 6 months in a far-away village to complete his/her degree.

Answer 3

Principles are best practices to follow to allow scalable architecture and software craftmanship. Design patterns are techniques about how to do the design and architect your code. Each design pattern has a different use case and is applicable to a different scenario. On the other hand principles ; in most cases you need to follow them to have code quality. And yes some principles imply some design patterns : Ex. Open/Closed principle closely implies strategy pattern . Dependency injection has strong ties to MVC pattern.