Implement muxing routing cache #851
Open
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
JAORMX
force-pushed
the
mux-routing-cache
branch
from
bc42187 to
76d9bba
Compare
This allows us to have a parsed and in-memory representation of the routing rule engine. The intent is to reduce calls to the database. This is more expensive to maintain since we need to refresh the cache on every operation pertaining to models, endpoints, workspaces, and muxes themselves. Signed-off-by: Juan Antonio Osorio <[email protected]>
Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
force-pushed
the
mux-routing-cache
branch
from
76d9bba to
f01d03e
Compare
Signed-off-by: Juan Antonio Osorio <[email protected]>
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.
This allows us to have a parsed and in-memory representation of the
routing rule engine. The intent is to reduce calls to the database.
This is more expensive to maintain since we need to refresh the cache on
every operation pertaining to models, endpoints, workspaces, and muxes themselves.
Finally, this implements the interface for matchers; Currently we only have one
"catch all" matcher, but this will change in the future.
Closes #786
Signed-off-by: Juan Antonio Osorio [email protected]