-
Notifications
You must be signed in to change notification settings - Fork 592
new feature: Add cache layer for opendal #5678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, I would like to work on this, can I? Or is anybody willing to work on this already? I thought about using https://github.com/foyer-rs/foyer. I see It has been already discussed here. |
Hi, @jorgehermo9, that will be greatly appreciated. No one is currently working on this. Ideally, our cache layer should enable users to design and implement their own cache algorithms while seamlessly switching between different cache crates like Foyer or Moka. However, I believe we should integrate with Foyer first to clarify our direction moving forward. Let's first build a FoyerLayer, and later, we can extract a CacheLayer from it. |
I agree a lot with the plan!! Thanks @Xuanwo 😊 |
Just as an update about this, I have the initial implementation almost finished (for read and blocking_read operations for the moment) and will submit a PR in a few days/a week, as soon as I can 😄 |
I have an idea that our future let cache_op = Operator::from_config(FoyerConfig::default).finish()?;
let op = op.layer(CacheLayer::new(cache_op)); We will need a benchmark to evaluate their performance. |
Provide high-quality built-in cache support in OpenDAL while ensuring users have the flexibility to implement their own caching logic.
The text was updated successfully, but these errors were encountered: