Set R · 5 sheets
Retries, caches, limits and background work. What keeps a shared system standing when one customer leans on it.
R-01 Resilience & Scale
Three retries and a two second wait is not a resilience strategy. It is a load generator with good intentions.
Drawn Nov 2013·Revised Jun 2025·7 min
R-02 Resilience & Scale
Two layers, one key format. If the tenant id is not in the key, the cache is a data leak with good response times.
Drawn Oct 2015·Revised Jan 2026·6 min
R-03 Resilience & Scale
The limit is not there to protect the API. It is there to protect the database that every other tenant is also using.
Drawn Nov 2022·Revised Dec 2025·6 min
R-04 Resilience & Scale
A BackgroundService with a timer is correct on one instance and wrong on two. The second instance is not a bug you can test for locally.
Drawn Oct 2018·Revised Apr 2026·6 min
R-05 Resilience & Scale
Five hundred identical virtual users prove nothing. Your tenants are three big ones and forty small ones, and only that shape finds the noisy neighbour.
Drawn Mar 2024·Revised Aug 2026·6 min