Sign in Subscribe

Software Architecture

Keep it together or split it? Making boundary decisions under uncertainty

Keep it together or split it? Making boundary decisions under uncertainty

You’ve explored the domain and defined boundaries - but what if you’re still not sure where to draw the line? Learn how to decide whether to keep responsibilities together or split them when uncertainty is unavoidable.

Ambivalent feelings about details in domain modeling

Ambivalent feelings about details in domain modeling

More detail doesn’t always mean better understanding. In domain modeling, too much creates noise, too little creates risk. The real challenge is deciding what truly matters - and accepting that detail is always a decision.

Knowledge reveals complexity - and improves Architecture

Knowledge reveals complexity - and improves Architecture

The more you understand the domain, the harder decisions become. That’s not a problem - it’s a signal. Architecture is not about simplifying reality, but about navigating its complexity and making better decisions despite uncertainty.

Software Architecture must evolve - or it becomes the Problem

Software Architecture must evolve - or it becomes the Problem

Architecture is often treated as something written in stone. In reality, software continuously changes - and architecture must evolve with it. The real danger isn’t changing architectural decisions. The danger is when they never change at all.

Domain Types: Build, buy, or outsource? (Part 2)

Domain Types: Build, buy, or outsource? (Part 2)

Architectural decisions evolve with knowledge. Domain classification provides direction, helping teams balance building, buying, and outsourcing as the system and market change.

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.