-
Notifications
You must be signed in to change notification settings - Fork 279
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
Redesign io.github.bucket4j.distributed.proxy.optimization package and make it officially released #415
Labels
Milestone
Comments
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
Nov 12, 2023
vladimir-bukhtoyarov
added a commit
that referenced
this issue
Nov 12, 2023
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
May 8, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
May 8, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
May 13, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
May 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rename Optimization to StorageSynchronizer
This naming will better describes the nature of object that tries to optimize the way to cummunicate with remote storage.
Introduce per ProxyManager storage-synchronizers
Currently, only per-bucket optimizations exist, this leads to API awkward when user need to cache strong reference to optimized buckets somewere as described in javadocs. At least for Batching optimization it is possible to store collection of optimized buckets inside ProxyManager itself, so storage synchronizers with ProxyManager scope will sserriously enhance user expirience.
Default optimization
It looks that
Batching
can be configured as default optimization for all integrations at ProxyManager level.Implement ScheduledStorageSynchronizer at ProxyManager level
It should sync all buckets with fixed frequence. At least following feature should be provided:
Documentation
Also it needs to document StorageSynchronizer.
The text was updated successfully, but these errors were encountered: