ADR-026 Home Database Cache #618
Merged
Conversation
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
robsdedude
requested changes
Feb 4, 2025
Co-authored-by: Robsdedude <[email protected]>
robsdedude
reviewed
Feb 12, 2025
Co-authored-by: Robsdedude <[email protected]>
Optimize SSR Tracking
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.
Added support for Bolt 5.8, which introduces a couple of useful features. The server now echoes back the resolved home/default database when starting a transaction, along with a connection hint indicating whether server-side routing (SSR) is enabled. If SSR is on, the echoed database can be used with an optimistic home database cache to predict a client-side route (optimistic routing), falling back to SSR if the guess is wrong. This can eliminate a round-trip, but only if all the following conditions are met: