From 0c54816b3f7115cfff1860d4be0f13568880a9f3 Mon Sep 17 00:00:00 2001 From: dsh Date: Wed, 8 May 2024 10:15:45 +0100 Subject: [PATCH] Removed empty AWS Content Link The linked content now results in a 404. --- .../100-mitigation-strategies/103-loadshifting.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/data/roadmaps/backend/content/123-scalability/100-mitigation-strategies/103-loadshifting.md b/src/data/roadmaps/backend/content/123-scalability/100-mitigation-strategies/103-loadshifting.md index d881761d2..0f39afe0e 100644 --- a/src/data/roadmaps/backend/content/123-scalability/100-mitigation-strategies/103-loadshifting.md +++ b/src/data/roadmaps/backend/content/123-scalability/100-mitigation-strategies/103-loadshifting.md @@ -9,7 +9,3 @@ There are several ways to implement load shifting in a cloud environment: - Auto-scaling: This involves automatically adjusting the number of resources that are available to a system based on the workload, allowing the system to scale up or down as needed. Load shifting is an important aspect of cloud design, as it helps to ensure that resources are used efficiently and that the system remains stable and available. It is often used in conjunction with other design patterns, such as throttling and backpressure, to provide a scalable and resilient cloud environment. - -Visit the following resources to learn more: - -- [Load Shifting - AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/serverless/patterns/load-shifting/)