![\"HA-store\"](\"https://ha-store.js.org/images/logo.png\"){kind=logo}
\n \n High-Availability store\n
\n [ <instance of a store>, ]| A list of storage tiers for the data. The order indicates where to look first. It's recommended to keep an instance of an in-memory store as the first one, and then expend to external stores like [redis](https://github.com/redis/node-redis). Check below for storage configurations.\nbatch | false |
{
delay: 50,
limit: 100
} | Batching options for the requests - `delay` is the amount of time to wait before sending the batch, `limit` is the maximum number of data items to send in a batch.\n\n*All options are in (ms)\n\n## Caching storage\n\nName | Default | Description\n--- | --- | ---\ninMemory | {
limit: 5000,
ttl: 300000
} | Caching options for the data - `limit` - the maximum number of records, and `ttl` - time to live for a record in milliseconds\n[redis](https://github.com/redis/node-redis) | {
ttl: 0,
keyspace: '',
host: '0.0.0.0',
path: null,
connection: <instance of redis connection>
} | Allows redis to act as a caching layer for ha-store. Keys are prefixed with the namespace. An existing connection handle can be passed. A new connection can be made via either `host` (IP, FQDN, etc) or `path` (Unix socket path)\n\n## Monitoring and events\n\nHA-store emits events to track cache hits, miss and outbound requests.\n\nEvent | Format | Description\n--- | --- | ---\nlocalCacheHit | `