You're reading from AWS for Solutions Architects Design your cloud infrastructure by implementing DevOps, containers, and Amazon Web Services

Product type Paperback

Published in Feb 2021

Publisher Packt

ISBN-13 9781789539233

Length 454 pages

Edition 1st Edition

Tools

AWS

Concepts

Cloud Computing

Table of Contents (20) Chapters

Preface

1. Section 1: Exploring AWS

2. Chapter 1: Understanding AWS Cloud Principles and Key Characteristics FREE CHAPTER

3. Chapter 2: Leveraging the Cloud for Digital Transformation

4. Section 2: AWS Service Offerings and Use Cases

5. Chapter 3: Storage in AWS – Choosing the Right Tool for the Job

6. Chapter 4: Harnessing the Power of Cloud Computing

7. Chapter 5: Selecting the Right Database Service

8. Chapter 6: Amazon Athena – Combining the Simplicity of Files with the Power of SQL

9. Chapter 7: AWS Glue – Extracting, Transforming, and Loading Data the Simple Way

10. Chapter 8: Best Practices for Application Security, Identity, and Compliance

11. Section 3: Applying Architectural Patterns and Reference Architectures

12. Chapter 9: Serverless and Container Patterns

13. Chapter 10: Microservice and Event-Driven Architectures

14. Chapter 11: Domain-Driven Design

15. Chapter 12: Data Lake Patterns – Integrating Your Data across the Enterprise

16. Chapter 13: Availability, Reliability, and Scalability Patterns

17. Section 4: Hands-On Labs

18. Chapter 14: Hands-On Lab and Use Case

19. Other Books You May Enjoy

Leave a review - let other readers know what you think

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. This might seem overwhelming, and perhaps we confused you. It is important to note that when building your own microservices, many of the services listed will not be used. Your job as an architect is to be able to discern which one is the right tool for your given business requirements. Another important consideration when choosing services is to make sure that the architecture you propose fits with the culture of the company. 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.