matrix-org / matrix-org/remember-this-rs
Not all caches should be able to persist forever
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
**Use case 1** I'm looking at immutable data acquired e.g. through a database or a web service. For performance reasons, I want it cached in-memory/on-disk as long as the data is useful. If I forget the data because it's too old and I suddenly need it again, I'll refetch it from its source and get the same data.
**Use case 2** I'm looking at live data acquired e.g. through a database or a web service. For performance reasons, I want it cached in-memory/on-disk. However, after e.g. one hour, this data is stale and should be cleared from memory/disk.
We currently (mostly) implement use case 1. We should also implement use case 2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the crate's existing in-memory and on-disk cache behavior to understand how cached data is stored and retrieved. Define how callers specify or apply an expiration period, then verify that live data is cleared after its lifetime while immutable data can still remain cached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100