nest-react-websockets VS Redis

Download the repository at this commit to follow along.

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).

This point relates to the previous one. Redis has several strategies for when it runs out of memory. You can remove the latest keys, random keys, etc. Intuitively, you might think that setting maxmemory to remove the oldest keys would remove the oldest messages and everything would be fine. However, that's not the case: https://github.com/redis/redis/issues/4543. The problem is that "key" is a keyword. In Redis streams, a stream references a key in terms of Redis. So, if you set this policy to LRU, LFU, or Random, and stream is like any other key, it can be removed entirely.

Redis is also an in-memory system with exceptional performance. But unlike Memcached, Redis is known as a "data structure server." It doesn't just support simple key-value pairs; it offers a rich variety of complex data structures like Lists, Hashes, Sets, and Sorted Sets.

redis.io Github

Caching, at a certain scale it makes sense to add caching to speed up requests, for example use Redis via the Redis Cache plugin

We are so delighted to partner with Redis for a new DEV challenge!

Redis as caching layer