Scalability's involvement with Application Rate Limiting architecture

A Rate Limiting Working Group was formed with the goal to Develop a recommendation for the preferred way to implement application rate limits within GitLab. An outcome of this was the Rate Limiting Blueprint.

The working group was formed by people who feel passionate about improving our current rate limiting implementation. However, to deliver a new framework, as outlined in the blueprint, will require dedicated engineering effort. There is an open conversation as to who would be best placed to lead on this effort. ~"team::Frameworks" are a candidate - the primary reason being that Consolidate on our tooling across the company to improve efficiency (from the blueprint) aligns with part of the mission of the Frameworks team.

[Open Questions: Why is it important? Objective metrics?]