Sign in Subscribe

Latest

Domain Types: Identifying core, supporting, and generic domains (Part 1)

Domain Types: Identifying core, supporting, and generic domains (Part 1)

Not all domains are equally important. Domain-Driven Design classifies them into core, supporting, and generic domains, helping teams focus their effort where the business gains the most competitive advantage.

Ubiquitous Language: Structuring knowledge into domains (Part 3)

Ubiquitous Language: Structuring knowledge into domains (Part 3)

The same word can mean different things in different domains. Identifying these differences helps reveal domain boundaries and ensures the language within each domain remains clear and unambiguous.

Ubiquitous Language: Words that reveal domains (Part 2)

Ubiquitous Language: Words that reveal domains (Part 2)

Language is a powerful tool for discovering domain boundaries. By analyzing terms, meanings, and context, teams can better structure their systems around real business knowledge.

Ubiquitous Language: Stopping the translation game (Part 1)

Ubiquitous Language: Stopping the translation game (Part 1)

Ubiquitous Language is a core Domain-Driven Design pattern that aligns developers and domain experts through a shared vocabulary used consistently in conversations, documentation, APIs, and code.

The strategic and tactical sides of Domain-Driven Design

The strategic and tactical sides of Domain-Driven Design

Domain-Driven Design improves collaboration, system evolution, and onboarding by embedding domain knowledge directly into code and establishing clear architectural boundaries.

Mind the gap between problem and solution spaces

Mind the gap between problem and solution spaces

Every system starts with a Problem Space - the needs, issues, and expectations of stakeholders. The Solution Space defines how we address those problems through design and architecture.

The good, the bad and the boundaries

The good, the bad and the boundaries

Good architecture is not about choosing one type of boundary. It’s about combining domain, technical, and infrastructure perspectives to design systems that evolve with growing knowledge.