Describe the decoupled limits service in the blueprint
What does this MR do and why?
This merge request describes the idea of having a Decoupled Limits Service, and explains how it is different from GitLab Policy Service.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
changed milestone to %15.5
added Architecture Evolution Blueprint sectionops labels
assigned to @grzesiek
Suggested Reviewers (beta)
The individuals below may be good candidates to participate in the review based on various factors.
You can use slash commands in comments to quickly assign
/assign_reviewer @user1
.Suggested Reviewers @ayufan
,@mbobin
,@andrewn
,@ekigbo
,@jreporter
If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/357923
.Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".
@andrewn @marshall007 I updated the blueprint with the description of the Decoupled Limits Service and the explanation about when we should introduce it and how it is related to GitLab Policy Service. Can you please review this merge request? Thanks! /cc @sgoldstein
requested review from @marshall007 and @andrewn
- A deleted user
added documentation label
1 Warning Please add a merge request subtype to this merge request. 1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
doc/architecture/blueprints/rate_limiting/index.md
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by Ghost User- Resolved by Grzegorz Bizon
- Resolved by Grzegorz Bizon
@grzesiek - please see the following guidance and update this merge request.1 Error, 1 Warning Please add typebug typefeature, or typemaintenance label to this merge request. Please add a subtype label to this merge request. If you have added a type label and do not feel the purpose of this merge request matches one of the subtypes labels, please resolve this discussion.
- Resolved by Grzegorz Bizon
- Resolved by Grzegorz Bizon
- Resolved by Grzegorz Bizon
- Resolved by Grzegorz Bizon
added 1 commit
- 7a4cb742 - Copy-edit changes to rate limiting blueprint
added 1 commit
- b70ee066 - Add a note about the two limits / policy services to the blueprint
added typemaintenance label
enabled an automatic merge when the pipeline for f00310ee succeeds
Hi @grzesiek,
Please note that authors are not authorized to merge their own merge requests and need to seek another maintainer to merge.
For more information please refer to:
This message was generated automatically. You're welcome to improve it.
added self-merge label
mentioned in commit 7674af9e
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label