nuts-foundation / nuts-foundation/nuts-node
Consider have persistent caching DID documents
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
We do have caching for it (mainly for speeding up DID resolving), but only in-memory. If an issuer's DID document becomes unavailable for whatever reason, things break in practice. We could quite easily mitigate this by making the cache persistent (e.g. in SQL or Redis/etc)
Contributor guide
No contributing guide indexed for this repository
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 locating the existing in-memory DID document cache and the DID resolution entry point; the issue does not name files or tests. Compare how a persistent cache would fit the current resolver and confirm that cached documents remain available after an issuer becomes unavailable, including across process restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100