npmjs.org : lock_and_cache_manager : 4.7.0
Most caching libraries don't do locking, meaning that >1 process can be calculating a cached value at the same time. Since you presumably cache things because they cost CPU, database reads, or money, doesn't it make sense to lock while caching?
Registry -
Download -
JSON -
codemeta.json
purl: pkg:npm/lock_and_cache_manager@4.7.0
Published:
Indexed:
Related tag:
v4.7.0
Loading...
Readme
Loading...
Dependencies
- @babel/cli ^7.4.3 Development
- @babel/core ^7.4.3 Development
- @babel/node ^7.2.2 Development
- @babel/plugin-proposal-object-rest-spread ^7.4.3 Development
- @babel/preset-env ^7.4.3 Development
- babel-eslint ^10.0.1 Development
- eslint ^5.16.0 Development
- git-validate ^2.1.4 Development
- standard ^7.1.1 Development
- tape ^4.10.1 Development
- tape-promise ^4.0.0 Development
- cache-manager ^2.9.0
- cache-manager-redis-store ^1.5.0
- death ^1.1.0
- redis ^2.6.2
- redlock ^2.0.0