Readyset is a MySQL and Postgres wire-compatible caching layer that sits in front of existing databases to speed up queries and horizontally scale read throughput. Under the hood, ReadySet caches the results of cached select statements and incrementally updates these results over time as the underlying data changes.
We have a forked version of rocksdb that is little over one year and almost 1000 commits out of date (as June 2024). We are on v8.1.1 with a few custom patches; the current release is v9.2.1.
There's two implementation options:
forward port our custom patches onto the most current upstream version. (It's probably easiest to cherry-pick the commits versus trying to rebase).
forget all of our custom patches and find alternatives within Readyset to the changes we made to the libraries.
Change in user-visible behavior
Possibly - if the process for an end user is not seamless, we will need some mechanism to help them upgrade from the previous version to the new version.
Description
We have a forked version of rocksdb that is little over one year and almost 1000 commits out of date (as June 2024). We are on v8.1.1 with a few custom patches; the current release is v9.2.1.
There's two implementation options:
Change in user-visible behavior
Possibly - if the process for an end user is not seamless, we will need some mechanism to help them upgrade from the previous version to the new version.
Requires documentation change