Domain-driven Design

Q: "What's the scope of embarc's consulting on strategic Domain-driven Design?"

"The range spans from one-off workshops (e.g. Event Storming), through working out various models when starting from a greenfield, all the way to restructuring the architecture of your service landscape during a migration from monolith to microservices."

Q: "What's the time horizon of this service?"

"In a relatively short time frame, we can hand you methods and best practices. Over a longer period, we can dive into the depths of your domain with you and help you bring order and quality into your systems as well as your communication paths."

Q: "What are the results of this consulting service?"

"Typical results are artifacts such as problem and risk analyses of existing models and services, fully worked-out models and model changes, or an architecture vision for redesigning your software."

Q: "Can we also help ourselves afterwards?"

"It's important to us that we don't just support you in your work, but also enable you to define good models and services yourself. We don't just suggest models and service cuts to you. We give you the tools and guiding questions to create and assess these models, the services, and their interfaces yourself."

Actually deliver on the promises of agility and microservices

(Business) Domain-driven (Software) Design

An efficient and comprehensible modeling of the business domain is the foundation for good implementability of business requirements, cross-role communication, and, not least, for a good technical cut of the application and the achievement of quality goals.

Our Services

Event Storming and Domain Storytelling

Establish cross-team domain understanding and develop a shared language

Modularization and Service Cut

Cutting systems the right way

Contact →

Domain-driven Design Services at a Glance

What?

Using strategic Domain-driven Design (DDD), we help you pour your deep domain knowledge into a cleanly structured and differentiated model, define meaningful boundaries for models, and choose the right level of abstraction depending on context. Together we analyze your various subdomains and derive strategic decisions from them. Taking quality goals and team structures into account, we help you cut your services and design dependencies and interfaces. Last but not least, we enable you to apply DDD independently within your company.

When?

Especially during a massive architecture overhaul, such as the introduction of microservices, when the domain logic is barely maintainable anymore and many dependencies exist, or when every qualitative improvement always creates a regression somewhere else, it’s worth putting the modeling and cut of services to the test.

Why?

Build software that solves the problems and challenges of your business, instead of letting the software dictate your business model. Reduce effort and errors when implementing business requirements, and find the right cut for your software to achieve your quality goals. High consistency between the knowledge in the heads of domain experts and your software ensures smooth communication across different roles.

Did we spark your interest?

Verwenden Sie das Kontaktformular oder senden Sie Felix Kammerlander eine E-Mail.

Unsere Expertise

Our consultants bring a lot of practical knowledge to support you here: we have relevant experience modeling various domains across the widest range of industries, and methods like DDD aren’t something we only know from books. With our knowledge of software and organizational architectures, we also bring a broader perspective and think through the consequences of modeling and the technical cut of software across all areas.

Our articles, books and blog posts on this topic

Architecture cheat sheet
Domain-driven Design in der Praxis (German)
View the cheat sheet

Blog post
Kriterien für die Einführung von querschnittlichen Bounded Contexts (German)
Read the blog post

Blog post
Prinzipien für die Umsetzung querschnittlicher Bounded Contexts (German)
Read the blog post

FAQs

What's the scope of embarc's consulting on strategic Domain-driven Design?

The range spans from one-off workshops (e.g. Event Storming), through working out various models when starting from a greenfield, all the way to restructuring the architecture of your service landscape during a migration from monolith to microservices.

What's the time horizon of this service?

In a relatively short time frame, we can hand you methods and best practices. Over a longer period, we can dive into the depths of your domain with you and help you bring order and quality into your systems as well as your communication paths.

What are the results of this consulting service?

Typical results are artifacts such as problem and risk analyses of existing models and services, fully worked-out models and model changes, or an architecture vision for redesigning your software.

Can we also help ourselves afterwards?

It’s important to us that we don’t just support you in your work, but also enable you to define good models and services yourself. We don’t just suggest models and service cuts to you. We give you the tools and guiding questions to create and assess these models, the services, and their interfaces yourself.