Verified Commit 59418974 authored by Bob Van Landuyt's avatar Bob Van Landuyt 🔴
Browse files

docs: add cross-references to existing rate limiting design docs 

Point readers of the 2022 blueprint and the simplification doc
to the new unified rate limiting architecture document for the
detailed technical design.
parent 257308be

content/handbook/engineering/architecture/design-documents/rate_limiting/_index.md

+3 −1
Original line number Diff line number Diff line
@@ -404,7 +404,9 @@ hierarchy. Choosing a proper solution will require a thoughtful research. 


## Status



Request For Comments.

Accepted. The application-level framework described in this blueprint is being

implemented through labkit. For the detailed technical design, see the

[Unified Rate Limiting Architecture](../unified_rate_limiting/) design document.



## Timeline

content/handbook/engineering/architecture/design-documents/rate_limiting_simplification/_index.md

+4 −0
Original line number Diff line number Diff line
@@ -20,6 +20,10 @@ toc_hide: true 
<!-- This renders the design document header on the detail page, so don't remove it-->

{{< engineering/design-document-header >}}



> **Note:** The technical design for Phase 2 (application-level unification) and

> beyond is detailed in the [Unified Rate Limiting Architecture](../unified_rate_limiting/)

> design document. This document remains the high-level roadmap.



## Summary



As GitLab.com has evolved, we've introduced rate limits and throttling measures at many layers to enhance security and performance of our platform, ensuring availability and user satisfaction are at a desired level. These measures have often been reactionary, and we have not had a consistent strategy for defining and enforcing these limits.