Sign in Subscribe

Software Architecture

Is it time to modify boundaries of your bounded contexts?

Is it time to modify boundaries of your bounded contexts?

Your bounded contexts aren't set in stone. As your system evolves, their boundaries may stop serving you well. Discover six symptoms that indicate it's time to revisit them - and learn why not every symptom means you should make a change.

Bounded Contexts Are Not Services

Bounded Contexts Are Not Services

One bounded context does not automatically mean one microservice. Bounded contexts and services solve different problems, and understanding their relationship helps us design systems that are easier to evolve and maintain.

Subdomains vs. Bounded Contexts: similar boundaries, different purposes

Subdomains vs. Bounded Contexts: similar boundaries, different purposes

The same business concept doesn't always need the same model. In Domain-Driven Design, subdomains and Bounded Contexts serve different purposes, and understanding the distinction helps us make better architectural decisions.

Understanding Essential and Accidental Complexity

Understanding Essential and Accidental Complexity

Not all complexity comes from the problem. Some of it is introduced by the solution we choose. Understanding the difference between essential and accidental complexity helps us make better architectural decisions.

All Models Are Wrong, But Some Are Useful

All Models Are Wrong, But Some Are Useful

All models are incomplete. That's not a flaw - it's what makes them useful. The real challenge is deciding what belongs in the model and what should deliberately be left out.

Decoupling Archetypes: Identity Over Inheritance

Decoupling Archetypes: Identity Over Inheritance

Inheritance looks elegant until it couples your entire architecture. Learn why Business Archetypes should be connected by identity, not shared base classes, and how this keeps Bounded Contexts independent and maintainable.

Domain Types: Three Myths About Domain Types

Domain Types: Three Myths About Domain Types

Many teams treat domain types as implementation guidance. In reality, they are a tool for understanding the business first. Let's challenge three common myths that can shape your architecture decisions.