Design Patterns for Software Architects
Design patterns are named, reusable solutions to recurring design problems. Creational, structural and behavioural patterns apply inside a codebase, such as factory, adapter and strategy, while enterprise integration patterns describe how separate systems exchange messages, for example routers, translators and dead letter channels.
Stage: Patterns and Styles · Part of the Software Architect roadmap · Last reviewed 19 November 2026
What to learn in Design Patterns
- Use a factory or builder to isolate object creation
- Apply adapter or facade to hide an awkward interface
- Replace conditionals with the strategy pattern
- Use observer or mediator to decouple event handling
- Choose a message router or content-based filter for integration
- Explain a dead letter channel and why it is needed
Design Patterns interview questions
What is the difference between the adapter and facade patterns?
An adapter converts one interface into another that clients expect, usually wrapping a single class. A facade offers a simpler unified interface over a group of subsystems. Adapter fixes incompatibility, facade reduces complexity.
What is a dead letter channel?
It is a destination where messages are sent when they cannot be processed after retries, for example because of a bad format. It stops poison messages blocking a queue and lets engineers inspect and replay failures.
Where Design Patterns fits in the Software Architect roadmap
Design Patterns belongs to the Patterns and Styles stage (advanced level), which takes about 6 hours. Choose the right shape.
Other units in this stage
Back to the full Software Architect roadmap