I "re-invented" jitter back in 2010, when I developed an Erlang/OTP-based Pub/Sub server supporting up to 1M concurrent long polling connections per single topi

I "re-invented" jitter back in 2010, when I developed an Erlang/OTP-based Pub/Sub server supporting up to 1M concurrent long polling connections per single topic. After you published a message to that topic all 1M of them were closing a long polling HTTP request and immediately reconnecting. Which was causing a thundering herd problem [1], but I only learned this term much much later. The obvious solution was to add randomized delays to reconnects. Of course that was probably the easiest part of scaling that system. [1] https://en.wikipedia.org/wiki/Thundering_herd_problem https://en.wikipedia.org/wiki/Thundering_herd_problem