Require Redis Lua scripts with ease.
```javascript const redis = require('@maxdome/redis')(process.env.REDIS_URL);
OpenTelemetry instrumentation for `redis` database client for Redis
Generates CRC hashes for strings - for use by node redis clients to determine key slots.
Redis utilities for redis instrumentations
Javascript Redis protocol (RESP) parser
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.
Info output parser for Redis
Redis commands
Redis commands
Converts callback-based functions to ES6 Promises
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 library emulates ioredis by performing all operations in-memory.
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.
Redis store for node-cache-manager
An HTTP/REST based Redis client built on top of Upstash REST API.
Error classes used in node_redis
Redis client mock object for unit testing
Redis storage adapter for Keyv
The Socket.IO Redis adapter, allowing to broadcast events between several Socket.IO servers
The simplest possible model for redis-objects
Require Redis 2.6.0 or higher
Yet another Ruby distributed lock using Redis, with emphasis in transparency. Requires Redis >= 2.6.12, because it uses the new syntax for SET to easily implement the robust algorithm described in the SET command documentation (http://redis.io/commands/set).
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 Logstash filter plugin for storing and retrieving data from redis cache. This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gem_name. This gem is not a stand-alone program.
A Logstash filter plugin for storing and retrieving data from redis cache. This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gem_name. This gem is not a stand-alone program.
`qless` is meant to be a performant alternative to other queueing systems, with statistics collection, a browser interface, and strong guarantees about job losses. It's written as a collection of Lua scipts that are loaded into the Redis instance to be used, and then executed by the client library. As such, it's intended to be extremely easy to port to other languages, without sacrificing performance and not requiring a lot of logic replication between clients. Keep the Lua scripts updated, and your language-specific extension will also remain up to date.
RedisRpc is the easiest to use RPC library in the world. (No small claim!). This version is a repackage that only has Ruby implementation. Redis is a powerful in-memory data structure server that is useful for building fast distributed systems. Redis implements message queue functionality with its use of list data structures and the `LPOP`, `BLPOP`, and `RPUSH` commands. RedisRpc implements a lightweight RPC mechanism using Redis message queues to temporarily hold RPC request and response messages. These messages are encoded as JSON strings for portability. Many other RPC mechanisms are either programming language specific (e.g. Java RMI) or require boiler-plate code for explicit typing (e.g. Thrift). RedisRpc was designed to be extremely easy to use by eliminating boiler-plate code while also being programming language neutral. High performance was not an initial goal of RedisRpc and other RPC libraries are likely to have better performance. Instead, RedisRpc has better programmer performance; it lets you get something working immediately.
RedisRPC is the easiest to use RPC library in the world. (No small claim!) It has implementations in Ruby, PHP, and Python. Redis is a powerful in-memory data structure server that is useful for building fast distributed systems. Redis implements message queue functionality with its use of list data structures and the `LPOP`, `BLPOP`, and `RPUSH` commands. RedisRPC implements a lightweight RPC mechanism using Redis message queues to temporarily hold RPC request and response messages. These messages are encoded as JSON strings for portability. Many other RPC mechanisms are either programming language specific (e.g. Java RMI) or require boiler-plate code for explicit typing (e.g. Thrift). RedisRPC was designed to be extremely easy to use by eliminating boiler-plate code while also being programming language neutral. High performance was not an initial goal of RedisRPC and other RPC libraries are likely to have better performance. Instead, RedisRPC has better programmer performance; it lets you get something working immediately.
Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x. Resque is great. So is job processing with redis. Our biggest drawback has been that resque requires the class that will be processing a job to be loaded when the job is enqueued. But what happens when the implementing job is defined in a separate application and isn't currently loaded into memory? Enter Resque Remote. Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.
`reqless` is meant to be a performant alternative to other queueing systems, with statistics collection, a browser interface, and strong guarantees about job losses. It's written as a collection of Lua scipts that are loaded into the Redis instance to be used, and then executed by the client library. As such, it's intended to be extremely easy to port to other languages, without sacrificing performance and not requiring a lot of logic replication between clients. Keep the Lua scripts updated, and your language-specific extension will also remain up to date.
Flamingo makes it easy to wade through the Twitter Streaming API by handling all connectivity and resource management for you. You just tell it what to track and consume the information in a resque queue. Flamingo isn't a traditional ruby gem. You don't require it into your code. Instead, it's designed to run as a daemon like redis or mysql. It provides a REST interface to change the parameters sent to the Twitter Streaming resource. All events from the streaming API are placed on a resque job queue where your application can process them. CAVEAT EMPTOR: This gem is alpha code so act accordingly.
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.