Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Implementing Cloud Design Patterns for AWS

You're reading from   Implementing Cloud Design Patterns for AWS Create highly efficient design patterns for scalability, redundancy, and high availability in the AWS Cloud

Arrow left icon
Product type Paperback
Published in Apr 2015
Last Updated in Feb 2025
Publisher
ISBN-13 9781782177340
Length 228 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
 Young Young
Author Profile Icon Young
Young
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Introduction FREE CHAPTER 2. Basic Patterns 3. Patterns for High Availability 4. Patterns for Processing Static Data 5. Patterns for Processing Dynamic Data 6. Patterns for Uploading Data 7. Patterns for Databases 8. Patterns for Data Processing 9. Patterns for Operation and Maintenance 10. Patterns for Networking 11. Throw-away Environments Index

Multi-data center pattern

The multi-server pattern guarantees resiliency at the server level, but can introduce an edge case. If the data center that the UI instances are in, goes under maintenance or has hardware failures that propagate upwards to the instances themselves, they might affect the end users, which is not acceptable. The UI instances cannot or should not be clustered, but should be present across different availability zones. This spanning across availability zones presents datacenter redundancy and is presented in the multi-data center pattern.

The steps for this pattern are nearly identical to the steps in the previous pattern except for two key differences. The first key difference is that the load balancer itself must cross multiple availability zones through subnets.

Multi-data center pattern

The other key difference is that the instances attached to the load balancer should be in different availability zones. Since the load balancer is in two zones, the instances should be in each zone as well...

lock icon The rest of the chapter is locked
Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Implementing Cloud Design Patterns for AWS
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Modal Close icon
Modal Close icon