Redis utilities for redis instrumentations
A robust, performance-focused and full-featured Redis client for Node.js.
A modern, high performance Redis client
This package provides support for the [RedisBloom](https://redis.io/docs/data-types/probabilistic/) module, which adds additional probabilistic data structures to Redis.
OpenTelemetry instrumentation for `redis` database client for Redis
The source code and documentation for this package are in the main [node-redis](https://github.com/redis/node-redis) repo.
This package provides support for the [RedisJSON](https://redis.io/docs/latest/develop/data-types/json/) module, which adds JSON as a native data type to Redis.
This package provides support for the [RediSearch](https://redis.io/docs/interact/search-and-query/) module, which adds indexing and querying support for data stored in Redis Hashes or as JSON documents with the [RedisJSON](https://redis.io/docs/data-type
This package provides support for the [RedisTimeSeries](https://redis.io/docs/data-types/timeseries/) module, which adds a time series data structure to Redis.
Generates CRC hashes for strings - for use by node redis clients to determine key slots.
An HTTP/REST based Redis client built on top of Upstash REST API.
Javascript Redis protocol (RESP) parser
Redis storage adapter for Keyv
The Socket.IO Redis adapter, allowing to broadcast events between several Socket.IO servers
Redis commands
Info output parser for Redis
This library emulates ioredis by performing all operations in-memory.
A Redis store for the `express-rate-limit` middleware
Redis commands
<div align="center"> <h1 align="center">@upstash/core-analytics</h1> <h5>Serverless Analytics for Redis</h5> </div>
Websockets provider for Yjs
Redis session store for Connect
Distributed mutex and semaphore based on Redis
A programming model for software-defined state
Provides easy access and configuration to a single per-application/thread, optionally namespaced, redis client.
ClassyCAS provides private, centralized, cross-domain, platform-agnostic centralized authentication than can hook in with modern Ruby authentication systems.
Redis::Directory assumes a Redis installation running on a default port and database 0 that will contain connection information for various other Redis databases. For example, if you were using a Redis database to store the content of cached pages, and this was running on a cluster of two Redis instances, with multiple applications connecting partitioned by database, then your connection might look like this: require "redis" require "redis/distributed" # The ACME Corp database is #27 cache = Redis::Distributed.new "redis://redis.example:4400/27", "redis://redis.example:4401/27" Redis::Directory uses a centralized Redis database to store the connection information so you don't have to remember "magic numbers" for each client/database mapping, and can easily update port-numbers/hostnames, cluster-members as necessary. The same connection with Redis::Directory would look like this: require "redis_directory" cache = Redis::Directory.new("redis.example").connect("cache", "acme")
A centralized Redis-based lock to help you wait on throttled resources
Centralized rate limiting for multiple web servies, using Redis.
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace