Have you been finding it difficult to model the boundaries of your system’s microservices? Have you been slowed down by the technical complexity of your codebase? Has your team been stepping on each other’s toes? If your answers to any of these questions are yes, then applying Domain Driven Design to your microservices is likely to be useful to your team. 

One of the difficult choices in microservices architecture is coming up with boundaries and deciding whether a particular piece of code should be turned into a microservice. Technical teams often make this decision without taking a business perspective on what really makes sense. Using DDD the boundaries for microservices are better designed by bringing both technical and business teams together to achieve the project’s goals.

This book takes key concepts from DDD and applies them to microservices architecture. Using an example business domain, and end-to-end code examples, you’ll learn to design and implement microservices using DDD. You’ll also understand DDD’s relationships to data mesh, team topologies, and micro-frontends. Bring technical and business teams together and achieve your project’s goals.

The term Domain-Driven Design (DDD) was coined by Eric Evans in his seminal book, Domain-Driven Design: Tackling Complexity in the Heart of Software, published in 2003, and was well ahead of its time. In recent years, microservice architecture has gained a lot of attention as one of the most popular evolutionary architecture styles. DDD is an immensely useful tool for designing scalable systems/platforms and a solid basis for designing better microservices architecture. DDD is also useful for building distributed data architectures including data mesh, and for organizing a large team using team topologies.

The audience for this book is software architects, enterprise architects, engineering managers and software engineers working on larger scale software platforms, ecosystems, and enterprise applications. My assumption is that they have some programming experience in the software industry.

Domain-driven design and microservices are both extremely popular topics. DDD covers architecture, data architecture, the organization of large teams on platforms and ecosystems, and micro-frontends, so it is likely to become key knowledge for most individuals working in the software industry at some point in their career.

By the end of this book the reader will understand:

• The relationship between Domain Driven Design (DDD) and microservices.
• How DDD can help with microservices architecture.
• How to use tactical and strategic DDD patterns.
• Why the domain model is the primary and most important layer in layered/tiered and hexagonal architectures.
• How to design domain events, which are the basis for event-driven architecture.
• Modular monolith architecture and its relation to DDD.
• Different types of Architectures - CQRS, Event Sourcing, Event Driven Architecture.
• How data mesh and team topologies are related to DDD.
• How micro-frontends are related to DDD

And the reader will be able to:

• Understand different architecture choices for implementing Domain Models.
• Come up with a microservice using the Domain Driven Design Aggregate concept. 
• Design and evolve better boundaries for microservices using DDD’s bounded context and ubiquitous language.
• Understand the Domain Layer and its importance in the overall success of the project.
• Apply DDD tactical patterns to existing codebases.
• Understand DDD strategic patterns like Ubiquitous language and Bounded Context.
• Understand the dynamics of the domain using Context maps describes relationships between bounded contexts.
• How to use Modular monolithic architecture in the context of Microservices or other architectures.
• Understand when you use CQRS, Event Sourcing, Event Driven Architecture.
• Using DDD in micro-frontends  applications