Building “The Better Store” an agile cloud-native ecommerce system on AWS — Part 2: Defining DDD Strategic Patterns

In Part One of Building the Better Store, I provided an introduction of an envisaged eCommerce website, and how Domain Driven Design (DDD) and its Strategic Patterns may be used to help compose a decoupled Microservices Architecture (MSA) that would promote its future change agility, scalability and fault-tolerance. This article focuses on illustrating and using these patterns for design of The Better Store. Introducing Domain Driven Design Domain Driven Design (DDD) is a methodology initially defined in 2003 in Eric Evan’s popular and well-received book ‘Domain-Driven Design: Tackling Complexity in the Heart of Software’ [1]. It is aimed at decomposing the complexity of a Problem Space (that is, a business’s functional domain/capabilities that are requiring development) into a domain model comprised of one or more decoupled and cohesive Bounded Contexts ; being sets of well-organised definitions of objects and business rules that share the same ubiquitous language understood by both b