multiplication

The passage around this formula

The second mechanism is spacing retries so that many failing clients do not recover in lockstep and immediately overwhelm the dependency that was already struggling. The AWS Architecture Blog’s canonical treatment of this problem, “Exponential Backoff and Jitter,” shows why backoff alone is insufient: if every client retries after exactly the same capped exponential delay, all of them retry at the same moment, reproducing the original overload the instant the dependency starts to recover [ 7 ] . Capped exponential backoff sets a ceiling, $\text{backoff}(n) = \min\!\left(\text{cap},\ \text{base} \cdot 2^{\,n}\right)$. and full jitter — the post’s recommended default — then draws the actual wait time as a uniform random value below that ceiling rather…

Read this part in the article →