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

High availability


One of the primary benefits of the public cloud is its geographical dispersion of resources. This distribution allows you to build highly available solutions at low cost. Availability covers a number of diverse topics. Depending on the customer, it can be measured in different ways. Traditionally, system uptime was the primary indicator. In the pre-cloud era, five nines was a good goal to have. This meant that your systems were up 99.999% of the time; downtime could be no more than five and a half minutes per year. As microservices became more prevalent in the cloud era, and systems got distributed across the globe, five nines became unrealistic. This is because complex systems inherently have more potential failure points and are more difficult to implement correctly. In a simple example with three components, each having five nines, the formula 99.999%*99.999%*99.999% = 99.997% illustrates how traditional measures of uptime start to break down in the cloud.

Amazon S3 has...