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

Different patterns


As your data volume grows, migrate toward toolsets that can handle your transformation and storage needs. To put it colorfully, avoid the bazooka, if all you need is a bow and arrow—there are others that could be used here hammer/nails for example. Continue to invest in new technologies where necessary, while ensuring that day-to-day business needs are kept stable, patched, and running.

 

Polyglot persistence

Taking advantage of the right technology for your persistence needs limits your exposure to unnecessary maintenance challenges. Microservice architectures give you the opportunity to choose the appropriate data structure for your business needs. When choosing a provider, factor in the learning and development costs, as well as the maintenance costs of your choice.

Technical debt often makes sense while rushing to get your product to market. As you pivot to meet your customers needs, data models can change rapidly. An unstructured notation may give you greater flexibility...