Building “The Better Store” an agile cloud-native ecommerce system on AWS — Part 3: DDD Tactical Patterns and App Architecture

Part Two of Building the Better Store described the use of DDD Strategic Patterns as tools for tackling complex requirements for a business system, by decomposing the problem domain to produce a high level design composed of decoupled ‘Bounded Contexts’; each of which may be considered as an initial blueprint for a Microservice. This article continues from the conceptual view produced in part two, and becomes more technically-focused on implementation details using DDD Tactical Patterns. Introducing DDD Tactical Patterns DDD tactical patterns, also known as ‘model building blocks’, are used to help define static models for complex bounded contexts. The main patterns and their relationships are illustrated as: Figure 1: DDD Tactical Patterns where each of the patterns may be described as below: Figure 2: Table defining main tactical patterns, for designing a Bounded Context. Example: Order Bounded Context The Order bounded context was first introduced in my Part 2: Defining Defining DDD