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

Testing your environment


As we move workloads to the cloud, we have the benefit of nearly unlimited capacity. In Chapter 3, Availability Patterns - Understanding Your Needs, we looked into how we could create an auto-scaling group. The resource we created used Spot Instances, a low-cost ephemeral compute capacity, to increase our number of instances: 

scaling_adjustment = 4
  adjustment_type = "ChangeInCapacity"

In the Persistence Patterns section of the book, we will dive into how to use our AWS metrics to choose what to measure. For now, we need to understand that whatever we choose as our default will at some point be suboptimal. Odds are that it will be on initial creation. We must constantly be validating our assumptions about what we've built.

 

 

Load testing with real data is one of the best ways to substantiate we are moving in the right direction with our postulations. Our infrastructure-as-code solution provides a reproducible way to rebuild our entire product in another region or...