Opened 3 years ago
Closed 3 years ago
#33743 closed Cleanup/optimization (duplicate)
Add topic page on rate-limiting solutions for Django to the documentation
| Reported by: | Hrushikesh Vaidya | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 4.0 |
| Severity: | Normal | Keywords: | rate-limiting |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
As we are yet to reach consensus on how ticket 21289 should be fixed, and more discussion is needed on the topic of implementing rate-limiting, we should have something in the documentation (preferably a topic page) guiding people toward a few approaches on how they can implement rate-limiting in their applications, and maybe point them towards a few mature third-party packages. If/when we do add a rate-limiting solution, this page can be updated accordingly.
See also - the forum discussion and the mailing list discussion
Note:
See TracTickets
for help on using tickets.
Let's keep this referring to #21289 [*], but yes, if we can't close that ticket by fixing it then adding a topic page pointing folks to some options (and at least gesturing to the complexities) is better than nothing.
Normally we don't link to 3rd Party packages, but it seems reasonable in this case to point to the mature and stable django-axes and django-ratelimit (others?) — which are part of Jazzband — given that they're both good options and it's not clear how/if we can progress in core.
Rough outline (?): What is rate-limiting, you likely want a middleware, available options — I don't think it needs to be too long.
[*]: I'll close this as a duplicate.