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

Practices to avoid in general


There is going to be some overlap here with the previous section, but we will focus on behaviors at a higher level. As you move to the AWS cloud, you have an excuse to review your traditional methods to ensure they are still applicable. In most cases, the technology is not the largest inhibiting factor. A lack of shared understanding will be the biggest blocker.

The following sections cover some of the most common practices that should be avoided.

Silos

Conway's law (http://www.melconway.com/Home/Conways_Law.html) suggests that an organization is bound to create software that mimics its structure. Think about this as you move your workloads to the cloud. There is an opportunity to refactor your team, as well as your systems and software. Organizational design is out of the scope of this book, but we will touch on some patterns to aid you in implementing good development practices later in the chapter.

The outcome of those exercises will provide input to the desilofication...