What Is a Design Pattern in Software Engineering?

A design pattern is a reusable, general solution to a commonly occurring problem in software design — not finished code, but a template describing how to str...

Published October 6, 2026

A design pattern is a reusable, named solution to a common software design problem, such as how to create objects, structure classes or let objects communicate. Patterns give teams a shared vocabulary.

The concept

The classic catalogue from the 'Gang of Four' groups 23 patterns: creational (Singleton, Factory, Builder), structural (Adapter, Decorator, Facade) and behavioural (Observer, Strategy, Command).

A pattern is a template, not code to copy. Applying one where it is not needed adds complexity.

Three families

Creational → how objects are made (Factory, Builder, Singleton)
Structural → how objects fit together (Adapter, Facade, Decorator)
Behavioural → how objects interact (Observer, Strategy, Command)

Practical examples

Strategy: swap algorithms

const strategies = { flat: p => p, sale: p => p * 0.9 }
const price = strategies[mode](100)

Observer: notify listeners

button.addEventListener('click', handler)

Factory: hide construction

const createLogger = (type) => type === 'file' ? new FileLogger() : new ConsoleLogger()

Common mistakes

  • Forcing patterns into simple code.
  • Naming a class after a pattern without following it.
  • Copying UML instead of understanding the intent.

Key takeaways

  • Patterns are proven, named solutions.
  • Three families: creational, structural, behavioural.
  • Use them when the problem appears, not before.

FAQ

Are patterns language specific?

The ideas are general; some are built into languages (iterators, closures).

Which patterns should I learn first?

Strategy, Observer, Factory and Decorator are widely useful.

More General articles