ReadySet Core: next-generation SQL caching, freely available
11–20 of 59 posts
Re: ReadySet Core: next-generation SQL caching, freely available
#12BSL :(
> ReadySet is licensed under the BSL 1.1 license, converting to the open-source Apache 2.0 license after 4 years. The ReadySet team is hard at work getting the codebase ready to be hosted on Github.
Re: ReadySet Core: next-generation SQL caching, freely available
#13I love the concept. Not needing to have extra code and logic for a caching layer seems very nice. In my experience, I haven't ever been in a situation where I needed super heavy caching, but this seems like it gives it to you "for free". Interested to see if we see more of ReadySet in the future.
Re: ReadySet Core: next-generation SQL caching, freely available
#14Re: ReadySet Core: next-generation SQL caching, freely available
#15Do you have a sense for when people can try it? Most of our app is reads and we're using Rails + Redis and it's fine and sometimes a pain. Would love to try it.
Re: ReadySet Core: next-generation SQL caching, freely available
#16Is this really the case that queries can't be cached on traditional databases?
Re: ReadySet Core: next-generation SQL caching, freely available
#17Are you looking into spreading the dataflow even more down to the clients ? Think realtime subscription for complex queries over structured data.
Re: ReadySet Core: next-generation SQL caching, freely available
#18> Traditional databases would compute the results of this query from scratch every time it was issued. Is this really the case that queries can't be cached on traditional databases?
Re: ReadySet Core: next-generation SQL caching, freely available
#19I signed up for the waitlist! I noticed it asked about AWS, Azure, and GCP but we use Heroku. Hopefully, that won't put me too low on the list. Do you have a sense for when people can try it? Most of our app is reads and we're using Rails + Redis and it's fine and sometimes a pain. Would love to try it.
Re: ReadySet Core: next-generation SQL caching, freely available
#20> Traditional databases would compute the results of this query from scratch every time it was issued. Is this really the case that queries can't be cached on traditional databases?
For example, MySQL deprecated their query cache, but previously it would only cache until there were any writes to the tables that the queries were referencing https://dev.mysql.com/doc/refman/5.7/en/query-cache-configur...