Building “The Better Store” — Part 4: Implementing a Microservices Architecture with Cloud Native Patterns and AWS Services
The previous two articles of this series have provided introductions to Domain Driven Design principles, and how they may be used for defining an appropriate Microservice Architecture for our sampl...
Source: dev.to
The previous two articles of this series have provided introductions to Domain Driven Design principles, and how they may be used for defining an appropriate Microservice Architecture for our sample ‘The Better Store’ cloud-native ECommerce system. This article continues from the proposed DDD tactical design to formulate an implementation of our decomposed microservices, while describing and adopting popular cloud-native patterns to reap advantages that they provide. The focus here will be defining an implementation which has the following features scope, as defined in the previous Strategic Patterns section: Scenario 1: OrderPurchased **When **I submit valid Card details **And **Payment is approved **Then **My order details with cart details will be stored in the Order Repository **And **The order details will be eventually persisted to the reporting database **And **An electronic Receipt will be emailed to me **And **A shipping order is sent for Fulfilment **And **I will be directed