Batches commands like incrby, hincrby and sadd to Redis.
Turn Redis batch ops from Amphora into Neo4j Cypher queries
Redis client mock object for unit testing
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
A set of utils for faster development of GraphQL tools
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.
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 [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.
Simple async batch with concurrency control and progress reporting.
Generates CRC hashes for strings - for use by node redis clients to determine key slots.
Compact fork of rudder-node-sdk
An HTTP/REST based Redis client built on top of Upstash REST API.
Javascript Redis protocol (RESP) parser
Distributed test runner using Redis as a work queue. Push file paths to a Redis list, then multiple CI runners atomically steal batches and execute them via a configurable command.
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 minimal gem for safely pushing data onto redis and taking it back out in batches of any size. Designed to work well in a multi host/thread environment.
Provides an easy way to queue some messages and push them in batches.
A fluentd redis input plugin supporting batch operations
Redis-based mutex library for using with sidekiq jobs and batches.
Redis-related job classes for Bricolage batch framework
Send commands to a redis server in pipelined batches
influxdb-async_queue is an attempt to optimize influxdb interactions by aggregating metrics into batches through redis queue.
A work-stealing distributed test runner. Push test file paths to a Redis list, then multiple CI runners atomically steal batches and execute them via a pluggable adapter (CLI for any test runner, or in-process RSpec for maximum performance).
Provides batch loading (MGET / pipeline) for Redis::Objects attributes on ActiveRecord models, following the same design as ActiveRecord's `preload`. Supports counter, value, list, set, sorted_set, and hash_key types.
Instead of making ActiveRecord calls to change a counter field, write them to capacitor. They'll get summarized in a redis hash, with a separate process batch-retrieving and writing to ActiveRecord. Being single-threaded, the writing process avoids row lock collisions, and absorbs traffic spikes by coalescing changes to the same row into one DB write.
Railscope provides deep insight into requests, exceptions, database queries, background jobs, view rendering, and Rake tasks in your Rails application. It features a React-based dark-themed dashboard, automatic sensitive data filtering, flexible storage backends (PostgreSQL and Redis), batch correlation of related events, and zero external gem dependencies beyond Rails itself.
This is a weak deduper to make things like bulk email run safer. It is not a lock safe for financial/security needs because it uses a weak redis locking pattern that can have race conditions. However, imagine a bulk email job that loops over 100 users, and enqueues a background email for each user. If the job fails at iteration 50, a retry would enqueue all the users again and many will receive dupes. This would continue multiple times as the parent job continued to rerun. By marking that a subjob has been enqueued, we can let that isolated job handle its own failures, and the batch enqueue job can run multiple times without re-enqueueing the same subjobs.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.