Data

Tools

Indexes

Applications

Experiments

Packages

An open API service providing package, version and dependency metadata of many open source software ecosystems and registries.

lock_and_cache

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?

Ecosystem
npmjs.org
Latest Release
5.3.9
about 7 years ago
Versions
37
Downloads
163 last month
Dependent Packages
1
@everything-registry/sub-chunk-2093 0.1.0 removed
npm install @everything-registry/sub-chunk-2093
1 version - Latest release: over 2 years ago - 152 stars on GitHub - 2 maintainers
@zalastax/nolb-lock 2023.1.24 removed
Subpackage of no-one-left-behind.
1 version - Latest release: over 3 years ago - 38 downloads last month - 110 stars on GitHub - 1 maintainer
Past Dependents
Include Past Dependents

Check this option to include packages that no longer depend on this package in their latest version but previously did.

Filter
Filter by Kind
All kinds runtime 2
Links
Registry npmjs.org
Source Repository
Homepage Homepage
JSON API View JSON
CodeMeta codemeta.json
Package Details
PURL pkg:npm/lock_and_cache
spec
License MIT
First Release over 10 years ago
Last Synced 1 day ago
Keywords
lock cache redis
Repository
Stars 2 on GitHub
Forks 0 on GitHub
repos.ecosyste.ms