-
Notifications
You must be signed in to change notification settings - Fork 2.6k
feat(standalone): support revision in API-driven standalone mode like etcd #12214
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
Conversation
1c4a014
to
17927e2
Compare
The title of this PR is not quite appropriate, it can be changed to: |
Hi, please also check the checklist items to make the pr clear |
Co-authored-by: Traky Deng <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree in principle with the PR and we can merge when you resolve all the issues on the documentation.
Co-authored-by: Zeping Bai <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doc LGTM
Description
In standalone mode, APISIX’s Admin API currently requires clients to retrieve the entire configuration on every sync. As configurations grow in size or change more often, this full-sync approach can lead to unnecessary network traffic and increased latency in applying updates. Moreover, frequent resource changes force a full rebuild of the internal radixtree, which significantly degrades lookup performance under heavy churn.
In the scenario of service discovery, the upstream will always update frequently, and we hope to only update the upstream without affecting the usage of other resources.
Control the changes of each resource by adding
<resource-type>_conf_version
:Checklist