Getting postgres sync going #15
Merged
Conversation
This file contains 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
added 5 commits
January 30, 2024 16:22
* planning on building a multi-bucket leaky bucket limiter * treat top bucket as the remaining relays (from billing) * buckets leak to lower buckets based on rate * bottom bucket decrements on successful relays * still setting up plugin system so critical logic is separated from business logic (should request go through)
* Added limiter type for cancelling flow * Auth is a special limiter * Setting up leaky bucket limiting, need to have some special wicks
* hooking up a couple more things, now gives 401 when quota runs out
* Listens for events (currently hardcoded) * Will push result of notification to redis
wtfsayo
approved these changes
Jan 31, 2024
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.
I want to push up my recent changes, it is on a few different fronts. There are some rate limiting attempts (currently counts down the "QUOTA" value in redis until it is 0). But the last bit here is a postgres listener that watches for notify events so it can respond to them (add to redis). We'll watch specific tables and make sure our cache is as fresh as possible. There will also be a periodic push to postgres to keep the write side of the cache current. Open to comments or questions on this.