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

Service discovery


We have already explored one method that can assist with service discovery: the load balancer. Amazon provides three different types of load balancers, any of which could potentially front your service in a region. In Chapter 2, Core Services - Building Blocks for Your Product, we looked at load balancer health checks for monitoring your instances. In the Serverless section, we explored fronting our Lambda services with a load balancer. We could have added a health check for the serverless implementation as well. Creating a target group for ECS containers is another pattern available to us. Using a load balancer provides highly available internal or external service endpoints. There are also a number of other options we can use in conjunction with ELBs and ALBs.

Route 53 provides us with the ability to create global load balancers. In contrast to the ALB, which provides load balancing at the port level, Route 53 distributes traffic across hostnames using DNS. It is quite...