Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: switch from "leaky" to "token" bucket #1790

Merged
merged 1 commit into from
Dec 11, 2024
Merged

Conversation

jsha
Copy link
Contributor

@jsha jsha commented Dec 10, 2024

The two metaphors are mirrors of each other, and either works, but since we use the "token" bucket metaphor internally in Boulder, it's less confusing to use the same metaphor externally.

The two metaphors are mirrors of each other, and either works, but since we use
the "token" bucket metaphor internally in Boulder, it's less confusing to use
the same metaphor externally.
Copy link
Contributor

@aarongable aarongable left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Saying "token bucket" is not only more consistent, it's more correct. Generally, a token bucket it full of tokens (surprise!), which are spent by requests and regenerate at a steady rate. In contrast, a leaky bucket is generally full of requests, which are allowed to "leak" out of the bucket (be processed) at a steady rate. Leaky buckets result in much steadier traffic flow, but requires a queuing mechanism to store the requests while they wait in the bucket.

@aarongable aarongable merged commit 9bbe7cd into main Dec 11, 2024
5 checks passed
@aarongable aarongable deleted the token-not-leaky branch December 11, 2024 00:40
ludekjanda added a commit that referenced this pull request Dec 13, 2024
# Latest from Crowdin

- Updates in Danish, French, Hebrew, Hungarian, Korean, Russian,
Ukrainian, Chinese (China)

- Changes resulting from: 
  -  #1788
  - #1790
  - #1792
  - #1794

Co-authored-by: Ludek Janda <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants