An introduction to the use case

This chapter will allow you to combine and practice many concepts we have covered throughout this book. You’ll need to design the architecture of your system to scale without impacting application performance. You can use a serverless architecture, which involves building small, independent functions triggered by events, such as changes in a database or the arrival of a new message. This allows you to scale your system as needed, paying only for the resources you use.

To build upon your existing knowledge, let’s go into more detail about implementing domain-driven design for a retail e-commence application use case that you learned about in Chapter 14, Microservice Architectures in AWS, under the section Domain-Driven Design. Let’s take a trip down memory lane to understand the use case.

To make it a fun learning experience, we’ll give a name to the retail store we will use to learn AWS, let’s name it AWSome...