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

Using multiple environments


To minimize risk during our deployments, we can create our product in a non-production environment. In our case, we will designate the AWS west region as our test location. A common practice for tiered environments includes development, testing, staging, and production. Everything below, or to the left of, production is grouped as non-production. Often there is considerable overlap in the functionality of the environments and in many organizations; they exist within the same cloud.

Our goal is to have non-production environments that have parity with production. However, as we discussed earlier, our service levels do not need to be as high in some non-production aspects. Since our data is not real, consistency is a less important piece of the puzzle for developers in their environment, whereas the test environments may need a truly durable environment to run stress tests on your systems.

Staging may be done within production if your deployment strategies allow you...