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

Chapter 9. Antipatterns - Avoiding Counterproductive Solutions

We have looked at a number of good processes, practices, and patterns for the AWS cloud. Now, we will explore some that you want to avoid. Some of the examples that follow are going to be countered by using the items in the first two sections. Others are not inherently technology problems. You should be aware of the smells that they bring and change course when you run into them. As your cloud craftsmanship improves, they will be easier to spot before implementation. At the beginning of your cloud journey, we expect failure to occur all the time. Be aware that refactoring is always going to be an option moving past your minimum viable product. Often, speed is the most important dimension to your product success. Taking on technical debt may be required to increase market shares or drive new features.

We will briefly cover the following topics in this chapter:

  • Exploring counterproductive processes
  • Practices to avoid in general
  • Anti...