Tactical Pattern Overengineering

Tactical DDD patterns increase complexity without corresponding domain value.

Use this profile to understand the building block briefly, place it in the model, and open related building blocks.

Content type

Concept

Theoretical construct: explains a term, principle, or mental model.

Classification level

Element

Concrete cog in the system that works inside larger relationships.

In brief

Taktisches Pattern-Overengineering in brief

Tactical pattern overengineering introduces DDD patterns even when their extra value does not justify the complexity.

Where does it come from?

The term arises from the tension between Domain-Driven Design and the XP principle YAGNI. Eric Evans catalogued tactical DDD patterns for domain models; the Simple Design discussion warns against building future requirements into today’s structure.

The mental model

A pattern is an investment: it creates concepts and rules but also adds learning and change cost. Compare concrete domain value with extra indirection and introduce patterns when need is evidenced.

Key building blocks

Core idea

Tactical pattern overengineering introduces DDD patterns even when their extra value does not justify the complexity. Kontext und Begriff.

Mechanism

A pattern is an investment: it creates concepts and rules but also adds learning and change cost. Compare concrete domain value with extra indirection and introduce patterns when need is evidenced. Praktische Leitfrage.

Practice context

This distinction protects domain code from unnecessary abstraction. Teams can use patterns where they express rules or ease change while keeping simple places simple.

When is it useful?

This distinction protects domain code from unnecessary abstraction. Teams can use patterns where they express rules or ease change while keeping simple places simple.

Martin Fowler – YAGNI Martin Fowler – Domain Driven Design