mirror of
https://github.com/ByteByteGoHq/system-design-101.git
synced 2026-04-02 00:57:24 -04:00
ee4b7305a2
This PR adds all the guides from [Visual Guides](https://bytebytego.com/guides/) section on bytebytego to the repository with proper links. - [x] Markdown files for guides and categories are placed inside `data/guides` and `data/categories` - [x] Guide links in readme are auto-generated using `scripts/readme.ts`. Everytime you run the script `npm run update-readme`, it reads the categories and guides from the above mentioned folders, generate production links for guides and categories and populate the table of content in the readme. This ensures that any future guides and categories will automatically get added to the readme. - [x] Sorting inside the readme matches the actual category and guides sorting on production
32 lines
923 B
Markdown
32 lines
923 B
Markdown
---
|
|
title: "Resiliency Patterns"
|
|
description: "Explore cloud design patterns for building resilient systems."
|
|
image: "https://assets.bytebytego.com/diagrams/0316-reliciency-patterns.jpg"
|
|
createdAt: "2024-02-08"
|
|
draft: false
|
|
categories:
|
|
- cloud-distributed-systems
|
|
tags:
|
|
- "Resilience"
|
|
- "Design Patterns"
|
|
---
|
|
|
|
Have you noticed that the largest incidents are usually caused by something very small?
|
|
|
|
|
|
|
|
A minor error starts the snowball effect that keeps building up. Suddenly, everything is down.
|
|
|
|
Here are 8 cloud design patterns to reduce the damage done by failures.
|
|
|
|
* Timeout
|
|
* Retry
|
|
* Circuit breaker
|
|
* Rate limiting
|
|
* Load shedding
|
|
* Bulkhead
|
|
* Back pressure
|
|
* Let it crash
|
|
|
|
These patterns are usually not used alone. To apply them effectively, we need to understand why we need them, how they work, and their limitations.
|