Book Image

Implementing Cloud Design Patterns for AWS - Second Edition

By : Sean Keery, Clive Harber, Marcus Young
Book Image

Implementing Cloud Design Patterns for AWS - Second Edition

By: Sean Keery, Clive Harber, Marcus Young

Overview of this book

Whether you're just getting your feet wet in cloud infrastructure or already creating complex systems, this book will guide you through using the patterns to fit your system needs. Starting with patterns that cover basic processes such as source control and infrastructure-as-code, the book goes on to introduce cloud security practices. You'll then cover patterns of availability and scalability and get acquainted with the ephemeral nature of cloud environments. You'll also explore advanced DevOps patterns in operations and maintenance, before focusing on virtualization patterns such as containerization and serverless computing. In the final leg of your journey, this book will delve into data persistence and visualization patterns. You'll get to grips with architectures for processing static and dynamic data, as well as practices for managing streaming data. By the end of this book, you will be able to design applications that are tolerant of underlying hardware failures, resilient against an unexpected influx of data, and easy to manage and replicate.
Table of Contents (20 chapters)
Title Page
Dedication
About Packt
Contributors
Preface
Free Chapter
1
Introduction to Amazon Web Services
Index

Summary


In this chapter, we discussed patterns to help to reduce downtime due to faults and increase availability. We also discussed a few patterns that help to create more resilient tiers that can withstand AZ and regional outages. Finally, we looked at how you can use S3 policies to afford your storage these same benefits. We strongly recommend injecting failures into your production systems regularly and will broach the topic again in Chapter 6, Ephemeral Environments – Sandboxes for Experiments.

In the upcoming chapter, we will discuss patterns to keep your systems well defended in order to further boost uptime.

Note

Use terraform destroy any time you don't want to leave your resources running up the bill.