Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
hotcache
Advanced tools
Readme
A classic problem: the cold cache. Your application was just deployed, moments ago. Immediately it's being hit by many requests, but since the cache is empty (or "cold"), every request has to go the expensive route before it can be put in cache.
This module is a simple cache that alleviates the problem. It's async-, promise- and error-aware and it will only fetch something once when the cache is cold. Concurrent requests will be queued up and resolved when the fetch comes back with a value. In case of errors, the queued up elements are resolved, but the result is not cached.
It has the simplest API you've seen.
Node
npm install hotcache
Browser
bower install hotcache
or
<script type="text/javascript" src="hotcache.min.js"></script>
var Hotcache = require("hotcache") //Node only
// First create a cache
var cache = new Hotcache()
// Then access elements in it
cache.get("someKey", 5000, myAsyncFunction, arg1, arg2, argN, cb)
If "someKey" already exists in the cache, it'll be returned to the callback immediately and myAsyncFunction
will not be executed. If it's not in the cache, myAsyncFunction
will be executed with the listed arguments and the result will be passed to cb
. If that call was successful (meaning that it didn't pass an error to cb
as its first argument), then the result will be cached for the specified number of milliseconds (5000 in this example).
Note: Make sure to pass a callback (cb
), even if it's just an empty function.
Note: There can be from zero to as many arguments as needed.
That's it. It solves a very simple problem elegantly. Does one thing and does it well.
This is an adaptation of the original written in OCaml, which you can view here.
Version 1.0 brings support for Promises.
var Hotcache = require("hotcache") //Node only
// First create a cache
var cache = new Hotcache()
// Then access elements in it
cache.pget("someKey", 5000, myFunction, arg1, arg2, argN) // Returns a Promise object
// Both of these are valid:
cache.pget("my_key", 1000, (function(someParameter){
return "some value" // A naked value
}), "some parameter")
.then(function(res){
// res === "some value"
})
.catch(function(err){
// log possible errors
})
cache.pget("my_key", 1000, (function(someParameter){
return Promise.resolve("some value") // A Promise
}), "some parameter")
.then(function(res){
// res === "some value"
})
.catch(function(err){
// log possible errors
})
Non-promise return values are wrapped in a Promise. Errors that happen inside the function are wrapped in a failed Promise.
It uses the bluebird package if installed and otherwise uses the built-in Promise object.
You can use a different Promise library by passing it by reference to the constructor:
var cache = new Hotcache(myPromiseLibrary)
FAQs
Smart async cache
The npm package hotcache receives a total of 6 weekly downloads. As such, hotcache popularity was classified as not popular.
We found that hotcache demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.