Javascript Redis protocol (RESP) parser
implement your server with the redis protocol
A redis protocol implement for Node.js.
Streams of the [redis protocol](http://redis.io/topics/protocol)
Sermone a Redis protocol encoder for commands.
Redis Protocol Object/Document storage in collections
Encodes redis commands into redis protocol
Lightweight Redis Protocol Encode/Decode in NodeJS
Javascript Redis protocol (RESP) parser
Ultra fast conversion of commands and args to redis protocol writables.
Redis utilities for redis instrumentations
A robust, performance-focused and full-featured Redis client for Node.js.
[DepUp] Javascript Redis protocol (RESP) parser
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.
Client to connect to dataserve using the redis protocol
OpenTelemetry instrumentation for `redis` database client for Redis
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.
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.
The Socket.IO Redis adapter, allowing to broadcast events between several Socket.IO servers
An implementation of the RESP2 and RESP3 protocols.
Zero-copy RESP2 and RESP3 protocol parser and serializer
A no_std Redis client
RadixOx — Redis-compatible in-memory key-value store
High-performance Redis-compatible key-value store built with Rust
A common library for Inn
Structs and functions to implement the Redis protocol.
REdis Syntax Protocol (RESP) parser library without any dependency.
A transport agnostic RESP protocol client/server.
Redis protocol parser
An eventmachine-based implementation of the Redis protocol
An eventmachine-based implementation of the Redis protocol
An eventmachine-based implementation of the Redis protocol
Simple redis based queue protocol implementation
An eventmachine-based implementation of the Redis protocol and Redis cluster support
A library and protocol to allow disperate systems to ask a question via STOMP and receive an answer in return. Optionally, answers can be cached in Redis.
Remq is a Redis-based protocol for building fast, durable message queues. The Remq protocol is defined by a collection of Lua scripts (located at https://github.com/kainosnoema/remq) which effectively turn Redis into a capable message queue broker for fast inter-service communication. The Remq Ruby client library is built on top of these scripts, making it easy to build fast, durable message queues.
An EventMachine[http://rubyeventmachine.com/] based library for interacting with the very cool Redis[http://code.google.com/p/redis/] data store by Salvatore 'antirez' Sanfilippo. Modeled after eventmachine's implementation of the memcached protocol, and influenced by Ezra Zygmuntowicz's {redis-rb}[http://github.com/ezmobius/redis-rb/tree/master] library (distributed as part of Redis). This library is only useful when used as part of an application that relies on Event Machine's event loop. It implements an EM-based client protocol, which leverages the non-blocking nature of the EM interface to acheive significant parallelization without threads. WARNING: this library is my first attempt to write an evented client protocol, and isn't currently used in production anywhere. All that bit in the license about not being warranted to work for any particular purpose really applies.
RobotLab is a Ruby framework for building and orchestrating multi-robot LLM workflows. Built on ruby_llm, it provides robots with template-based prompts, tools, and shared memory; networks for coordinating multiple robots with intelligent routing; MCP (Model Context Protocol) integration for external tool servers; and a memory system with Redis backend and semantic caching. Optional gems add Rails integration (robot_lab-rails), durable learning (robot_lab-durable), Ractor concurrency (robot_lab-ractor), and document storage (robot_lab-document_store).
Log2json lets you read, filter and send logs as JSON objects via Unix pipes. It is inspired by Logstash, and is meant to be compatible with it at the JSON event/record level so that it can easily work with Kibana. Reading logs is done via a shell script(eg, `tail`) running in its own process. You then configure(see the `syslog2json` or the `nginxlog2json` script for examples) and run your filters in Ruby using the `Log2Json` module and its contained helper classes. `Log2Json` reads from stdin the logs(one log record per line), parses the log lines into JSON records, and then serializes and writes the records to stdout, which then can be piped to another process for processing or sending it to somewhere else. Currently, Log2json ships with a `tail-log` script that can be run as the input process. It's the same as using the Linux `tail` utility with the `-v -F` options except that it also tracks the positions(as the numbers of lines read from the beginning of the files) in a few files in the file system so that if the input process is interrupted, it can continue reading from where it left off next time if the files had been followed. This feature is similar to the sincedb feature in Logstash's file input. Note: If you don't need the tracking feature(ie, you are fine with always tailling from the end of file with `-v -F -n0`), then you can just use the `tail` utility that comes with your Linux distribution.(Or more specifically, the `tail` from the GNU coreutils). Other versions of the `tail` utility may also work, but are not tested. The input protocol expected by Log2json is very simple and documented in the source code. ** The `tail-log` script uses a patched version of `tail` from the GNU coreutils package. A binary of the `tail` utility compiled for Ubuntu 12.04 LTS is included with the Log2json gem. If the binary doesn't work for your distribution, then you'll need to get GNU coreutils-8.13, apply the patch(it can be found in the src/ directory of the installed gem), and then replace the bin/tail binary in the directory of the installed gem with your version of the binary. ** P.S. If you know of a way to configure and compile ONLY the tail program in coreutils, please let me know! The reason I'm not building tail post gem installation is that it takes too long to configure && make because that actually builds every utilties in coreutils. For shipping logs to Redis, there's the `lines2redis` script that can be used as the output process in the pipe. For shipping logs from Redis to ElasticSearch, Log2json provides a `redis2es` script. Finally here's an example of Log2json in action: From a client machine: tail-log /var/log/{sys,mail}log /var/log/{kern,auth}.log | syslog2json | queue=jsonlogs \ flush_size=20 \ flush_interval=30 \ lines2redis host.to.redis.server 6379 0 # use redis DB 0 On the Redis server: redis_queue=jsonlogs redis2es host.to.es.server Resources that help writing log2json filters: - look at log2json.rb source and example filters - http://grokdebug.herokuapp.com/ - http://www.ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/DateTime.html#method-i-strftime
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.
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.