connect multiple 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
Redis session store for Connect
TypeScript definitions for connect-redis
A graphql-subscriptions PubSub Engine using redis
Connect rate limiter
Redis utilities for redis instrumentations
The Socket.IO Redis adapter, allowing to broadcast events between several Socket.IO servers
Lock on asynchronous code
A robust, performance-focused and full-featured Redis client for Node.js.
The Socket.IO adapter based on Redis Streams, allowing to broadcast events between several Socket.IO servers
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.
Example usage: ```javascript import { createClient, Graph } from 'redis';
OpenTelemetry instrumentation for `redis` database client for Redis
Redis client mock object for unit testing
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 [RedisTimeSeries](https://redis.io/docs/data-types/timeseries/) module, which adds a time series data structure to Redis.
A locking primitive using redis.
Redis session store for your Sails app.
Node.js body parsing middleware
An HTTP/REST based Redis client built on top of Upstash REST API.
Bull / BullMQ queue command line REPL
handles multiple redis connections
universal redis driver to connect that allows for multiple transports
Three basic CRDTs (set, hashmap and counter) for redis. Also includes a ConnectionPool that allows you to run concurrent redis commands on multiple connections w/o using eventmachine/em-hiredis.
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")
LLM Chain is a powerful Ruby framework that provides tools for building sophisticated LLM-powered applications. It includes support for prompt management, conversation chains, memory systems, vector storage integration, and seamless LLM provider connections. Key features: • Chain-based conversation flows • Memory management with Redis • Vector storage with Weaviate • Multiple LLM provider support • Prompt templating and management • Easy integration with existing Ruby applications
No description provided.
No description provided.
No description provided.