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

Chapter 14: Hands-On Lab and Use Case

In this chapter, we will put together many of the concepts that we learned about in previous chapters to build a practical, generic web UI serverless architecture. After reading this chapter, you should be able to use the concepts to build your own application using some or all of the components that we will review in this chapter.

For many of the services, you will be able to pick and choose the services that will be used in the applications you develop. For example, your application may be more user-centric and may not require any asynchronous services. In this case, you can pull the asynchronous component out of your architecture. However, for some of the services, it is highly advisable that you make sure you include them in your architecture. For example, if your application is going to have a frontend, you will want to ensure that you have an authentication component so that every user is authenticated before using any of the other services...