You're reading from AWS for Solutions Architects The definitive guide to AWS Solutions Architecture for migrating to, building, scaling, and succeeding in the cloud

Product type Paperback

Published in Apr 2023

Publisher Packt

ISBN-13 9781803238951

Length 692 pages

Edition 2nd Edition

Tools

AWS

Concepts

Cloud Computing

Authors (4):

Neelanjali Srivastav

Saurabh Shrivastava

Alberto Artasanchez

Imtiaz Sayed

View More author details

Table of Contents (19) Chapters

AWS for Solutions Architects, Second Edition: Design your cloud infrastructure by implementing DevOps, containers, and Amazon Web Services

1 Understanding AWS Principles and Key Characteristics FREE CHAPTER

2 Understanding AWS Well-Architected Framework and Getting Certified

3 Leveraging the Cloud for Digital Transformation

4 Networking in AWS

5 Storage in AWS – Choosing the Right Tool for the Job

6 Harnessing the Power of Cloud Computing

7 Selecting the Right Database Service

8 Best Practices for Application Security, Identity, and Compliance

9 Dive efficiency with Cloud Operation Automation and DevOps in AWS

10 Bigdata and streaming data processing in AWS

11 Datawarehouse, Data Query and Visualization in AWS

12 Machine Learning, IoT, and Blockchain in AWS

13 Containers in AWS

14 Microservice and Event-Driven Architectures

15 Domain-Driven Design

16 Data Lake Patterns – Integrating Your Data across the Enterprise

17 Availability, Reliability, and Scalability Patterns

18 AWS Hands-On Lab and Use Case

Domain-driven design

DDD might fall into the shiny object category, as many people see it as the latest trendy pattern. However, DDD builds upon decades of evolutionary software design and engineering wisdom.

To better understand it, let's briefly look at how the ideas behind DDD came about.

History of domain-driven design

DDD has its roots in the Object-Oriented Programming (OOP) concepts pioneered by Alan Key and Ivan Sutherland. The term OOP was coined by Alan Key around 1966 or 1967 while in grad school.

Ivan Sutherland created an application called Sketchpad, an early inspiration for OOP. Sutherland started working on this application in 1963. In this early version of an OOP application, objects were primitive data structures displayed as images on the screen. They started using the concept of inheritance even in those early days. Sketchpad has some similarities with JavaScript's prototypal inheritance.

OOP came about because developers and...