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

Microservice examples

In the previous section, we packed a lot of information into a small space. We listed and discussed a lot of AWS services that can be used to build microservices. It is important to note that many of the services listed will not be used when building your microservices. Your job as an architect is to discern which one is the right tool for your given business requirements. Another important consideration when choosing services is to ensure that the architecture you propose fits with the company's culture. For example, you might not want to recommend using Java as the programming language for the microservices if the current client is a Microsoft shop—C# might be a better recommendation. Let's try to dial it down and now work on a simple microservice example using DDD.