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

Desilofication


The cloud is all about breaking down patterns that have solidified in traditional enterprises. Specialization has reinforced these practices. A networking expert in a siloed organization often does not have to care about how their design affects the paying customer. This occurs because that professional is seeing a blinkered view of their clients. 

As we create or move workloads to the cloud, we have the opportunity to demolish these standalone knowledge depots. Desilofication is the process of breaking down barriers to knowledge caused by separate organizations not cooperating or being aware of the other's existence.

Product mindset

Our product mindset encourages us to seek out and understand the business outcomes of our users. Understanding that our instances must have an IP address doesn't really tell us anything about business value. Knowing that all credit card transactions need to be approved, or denied, in under three seconds provides us with a lot more context. 

The difference...