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

Best practices


Avoid one size fits all solutions. One size doesn't usually fit all situations that you might need to cater for. Think about the various needs of your application/use cases and design accordingly some things to consider, such as document storage, relational storage, graph storage, caching, data stream processing, image processing, high availability, high consistency, distributed nodes, latency, transaction support. This list is not exhaustive.

Take time to fully understand the life cycle of your tools of choice and data that you are charged with caring for. This includes tool upgrade time frames and assessing compatibility issues after upgrade. High incidences of upgrades for a toolchain might be a consideration for discounting it for production services as there may be stability or compatibility issues between versions.

Where practical, find the bleeding edge for your toolchain and map your journey to it. It will pay dividends if you understand upcoming features so you can...