ReadySet is a transparent database cache for Postgres & MySQL that gives you the performance and scalability of an in-memory key-value store without requiring that you rewrite your app or manually handle cache invalidation. ReadySet sits between your application and database and turns even the most complex SQL reads into lightning-fast lookups. Unlike other caching solutions, it keeps cached query results in sync with your database automatically by utilizing your database’s replication stream. It is wire-compatible with Postgres and MySQL and can be used along with your current ORM or database client.
⭐ If you find ReadySet useful, please consider giving us a star on GitHub! Your support helps us continue to innovate and deliver exciting new features.
See here.
- Interactive demo: interactive walk through of ReadySet’s features.
- Getting started guide: instructions for how to connect ReadySet to your database and start caching queries.
- Why ReadySet: explains the motivation behind ReadySet and how it compares to traditional database caching.
- Documentation: more in-depth information about how to use ReadySet.
- Blog: articles from the ReadySet universe.
For general help using ReadySet, see our official docs. For additional help, you can use one of these channels to ask questions, or give us feedback:
- Slack: Discussions with the community and the team.
- GitHub: For bug reports and feature requests.
- 𝕏 (Twitter): For product updates and other news.
Check out our roadmap to learn more about what's coming next for ReadySet.
We welcome contributions! Here are a few helpful links to get you started:
- Guide to build ReadySet from source
- Good first issues for first-time contributors
- Github issues link to suggest bug fixes and features
- #source-code channel in Slack to discuss larger projects
ReadySet is licensed under the BSL 1.1 license, converting to the open-source Apache 2.0 license after 4 years. It is free to use on any number of nodes.