Re: [PR] feat: initial cache layer implementation [opendal]

["MrCroxx (via GitHub)" <gi...@apache.org>]

MrCroxx commented on PR #5906:
URL: https://github.com/apache/opendal/pull/5906#issuecomment-2774594612

   > What I mean is, if a key gets deleted or updated, we should refresh the cache. Otherwise, we'll end up with stale data.
   
   That's true. However, foyer has a lot of room for optimization when handling deletion and updatable data for now. Currently, in almost all user scenarios in Foyer, deleted data is not read, and existing data is not updated. Although Foyer has already made relevant designs and optimizations (e.g., tombstone log to ensure that delete is also append-only), it is not commonly used, so it still needs to be validated and optimized.
   
   Therefore, for scenarios that require access to deleted data or updatable needs, I think Foyer should not be considered for use in the production environment for the time being. 
   
   However, based on my current experience, such scenarios are not very common.
   
   Moreover, other similar cache systems also have some corner cases or performance issues in terms of consistency. We can discuss together how to improve it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org