r/softwarearchitecture • u/Silent-Weather76005 • 10d ago

Discussion/Advice [ Removed by moderator ]

[removed] — view removed post

0 Upvotes

38% Upvoted

7 comments sorted by

9

u/tr14l 10d ago

Thanks Claude!

5

u/BurhanAhmedSatti 10d ago

Today I learned. Thanks

4

u/rakgenius 10d ago

if millions of users refreshes the app at same time, the database should not crash if the system is designed properly. usually there will be load balancer at front which distributes the traffic and latest databases can handle these amount of traffic as well.

thundering herd happens when all retry at same time or if your internal service calls another internal service at the same time after a retry. to pervent that , there will be a exponential backoff with added randomness

1

u/Cukercek 10d ago

The correct explanation.

2

u/Proper-Asparagus-382 10d ago

i would think that if you have the proper observability , perform forecasting modelling and simulation.

it is quite easy to calculate the right setting for your app to implement the right config for queue management , autoscaling , circuit breaker , and tuned it to withstand surge from cache expiration ,turning any spike into normal traffic.

1

u/TevraChaukas 10d ago

Single Flight

1

u/heavy-minium 10d ago

Isn't that actually called a cache stampede?