redis-rs VS Redis

https://github.com/redis-rs/redis-rs/issues/1419#issuecommen... - looks to be mostly resolved at this point, with Redis Inc. simply going to step up its contributions to the open-source version without taking control.

There is a new comment by antirez in the past few minutes: https://github.com/redis-rs/redis-rs/issues/1419#issuecommen...

The goto Redis client for Rust is called redis-rs. It has over 3k stars on Github. but I found it very annoying to use because I quickly found out that if you want to set any value you had to get a mutable reference to the underlying client. Which meant great pain to store Redis client in the global scope. People who do not know what a mutable reference is consider the let keyword in JavaScript. you can mutate or change a variable that is initiated with let.

staticpi, is a websocket forwarding service. Basically, it enables one to keep a Raspberry pi, or any computer, “connected”, in order to send and receive messages to and from any client, without having to deal with a static IP address, open ports on your router, or similar. Built in Rust, using axum, which in turn uses tungestine-rs for the websocket connections, tokio, sqlx, redis-rs and others.

redis (use streams and pubsub)

Are you addressing the long-standing issue that the redis client has related to dropped connections?

I switched to LALRPOP for gluon but I still use combine in https://github.com/mitsuhiko/redis-rs and some other projects which need to parse "protocols" (less need for good error messages/error recovery and more need for speed).

The project is implemented with MongoDB Rust driver and redis-rs crate.

Place Redis near the app for session and cache speed. See https://redis.io/.

My initial idea was to leverage the main application’s queue worker by deploying a queue worker remotely and setting up a secure connection between them using something like Wireguard. Vigilant is written in PHP using the Laravel framework, for queuing it uses Laravel Horizon. This is a queuing system built on top of Redis. All monitoring tasks in Vigilant are executed on this queue, it allows for multiple queues to exist identified by an unique name. Vigilant has queues for uptime, dns, lighthouse etc, this way the different monitors don’t block each other and resources can be managed per type of monitor. To start a queue worker we can run a single command in a container, exactly like the horizon container does now in the current Docker compose setup. So my first try was to deploy a remote Horizon worker that just handles one queue and name it something like uptime:de or uptime:us to specify the location. Horizon already runs in a separate Docker container.

Redis / RedisGraph - redis.io/

It's for investors AFAICT. When Masayoshi Son opens your home page it better say 'AI' in big bold letters.

Is your product a search engine? It's AI now. [1][2]

Is it a cache? Actually, it's AI. [3]

A load balancer? Believe it or not, AI. [4]

[1] https://www.elastic.co/

[2] https://vespa.ai/

[3] https://redis.io/

[4] https://www.f5.com/

The software is fully written in TypeScript and organized as an Nx workspace, utilizing the latest framework releases. The backend is based on NestJS in combination with PostgreSQL as a database together with Prisma and Redis for caching. The frontend is developed with Angular.

Here’s the thing: sometimes it’s not your database’s fault. What’s missing is a speed booster in your architecture: Redis.

Redis

This is the path of ultimate control. You spin up a Node.js server, add the socket.io library for WebSocket communication, and use a Redis instance to manage connection state and pub/sub messaging across multiple server instances.

Your Database: This is your system's memory. It can be a fast in-memory store like Redis for temporary data (perfect for velocity checks) or a persistent relational database like PostgreSQL for long-term data (like blacklists).