feat: add adaptive cache invalidation hooks for transaction state#875
Merged
Conversation
|
@dinahmaccodes Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
Author
|
@Junirezz |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Description
Backend: Adaptive Cache Invalidation Hooks (#637)
Implemented a hook-based system for triggering targeted cache invalidation when writes change dependent read models. The system allows registering invalidation hooks that return cache key patterns to clear based on transaction events.
Changes:
registerInvalidationHook()andtriggerCacheInvalidation()to cache middlewareBackend: Redis-Backed Adaptive Throttle (#862)
Enhanced the adaptive throttle middleware to use Redis for distributed state when
REDIS_URLis configured, enabling throttling to work across multiple backend instances.Changes:
RedisAbuseStoreclass that falls back to in-memory storage when Redis is unavailableredisClientManagerfrom rate limiteradaptive_throttle_block_countandadaptive_throttle_active_blocksBackend: Retry Budget Limits for RPC Dependencies (#630)
Introduced configurable retry budget controls to prevent runaway retries under upstream Soroban RPC failures.
Changes:
RetryBudgetServicewith configurable limits (max retries, window, success rate, failure threshold)sorobanClient.tswith exponential backoffretryWithBudget()helper that respects budget limitsRETRY_BUDGET_MAX_RETRIES,RETRY_BUDGET_WINDOW_MS,RETRY_BUDGET_MIN_SUCCESS_RATE,RETRY_BUDGET_FAILURE_THRESHOLDFrontend: Cross-Page Toast Center with Deduplication (#619)
Enhanced the toast notification system with deduplication to prevent showing identical toasts multiple times.
Changes:
dedupeKeyoption toToastOptionsfor custom deduplicationclearAll()method to dismiss all toastsChecklist
Closes #637
Closes #862
Closes #630
Closes #619