< session />

From Domain Driven Design (DDD) to Delivery

Domain-Driven Design (DDD) has been guiding large development projects since 2003, when Eric Evans’ seminal book was released. DDD is divided into two parts: Strategic and Tactical. One common issue is that the strategic part can become so involved that we lose focus on implementation. This presentation focuses on bridging strategy with implementation, exploring topics in pairs. For instance, when creating a bounded context, is it a microservice or part of a subdomain? When we create a domain event, how is it transformed into something actionable? And how do other tactical patterns fit into what we decide in the strategic phase?

In this presentation, we will break these ideas down into pairs of topics:

• Subdomains to Architecture Boundaries
• Where do Microservices fit in?
• Where does DataMesh fit in?
• How do subdomains and bounded contexts fit in?
• What is shared kernel technology-wise? Is it a library or a service?
• Where do we put human beings in all this?
• What can we afford to do?
• What kind of technology shopping list are we looking at?

Target Audience: This session is primarily aimed at Software Architects, as it focuses on applying Domain-Driven Design principles to align strategic goals with real-world implementations, particularly in relation to microservices and bounded contexts. Back-end Developers are the secondary audience, as they work closely with implementing DDD concepts and patterns in code and can benefit from understanding how tactical decisions align with strategic DDD principles. DataTech Professionals may also find value in discussions around DataMesh and how it fits within the DDD context.