|
|
|
|
|
|
by nicobn
2708 days ago
|
|
|
I've actually seen your hypothetical in action, but the bug was even more subtle. Assume service A, B and C. A and C both need information from each other which is usually cached. Normally, you'd deploy one service at a time so the call chain would go A -> B -> C -> A or A -> C then A -> B -> C but in this particular instance, A and C's caches were cold, causing an explosion of service calls that took both services down. |
|
|
Sounds like a monolith pulled apart :-)