Cache DID documents
Closed this issue · 1 comments
Description
A light-weight in-memory cache implementation can drastically speed up the resolution of non-deterministic DID methods (such as ˋdid:iotaˋ) to provide a smoother end-user experience. The cache should be optional and disabled by default. Since ˋdid-managerˋ supports externally-managed pre-funded DIDs that are only used by one entity (such as ˋssi-agentˋ), a caching solution can still be considered safe in terms of revocation and outdated data. A possible feature flag ˋincludeˋ could only include a list of DIDs to be cached, while non-matches would always be resolved on each request.
Motivation
Performance increase
Resources
No response
To-do List
- Implement in-memory cache
- Add configuration options with sensible defaults
🎉 This issue has been resolved in version 1.0.0-beta.2 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀