node-redis | A high performance Node.js Redis client | Runtime Evironment library

I am using node-redis. I have a cron job that updates my db and I have redis cache that caches the db response.

The problem I'm having is that my cron job runs everyday at 12am, however I can only set redis cache to expire in x seconds from now. Is there a way to make node-redis cache expire everyday at 12am exactly. Thanks.

Code:

I am using Node Redis with this config:

I have a Node.js web application which uses redis as session storage. Some requests receive the following ReplyError while trying to save the session:

I am trying to write a timer for a game. I decided to use Redis and Web Sockets to keep the timer consistent across multiple devices. I have a function that works however when I go to call it recursively with either setTimeout or setInterval I get a "Range Error: Maximum call stack size exceeded". I can not figure out how to bypass this error. Does anyone know if it has to do with the blocking nature of the node-redis publish method? I have attached the code below.

I am using node (TypeScript) and node-redis library. Since I use TypeScript, I also imported @types/redis.

In addition, I read this article on how to promisify redis methods for TypeScript usage: https://flaviocopes.com/node-promisify/

My problem is that is that it works for some redis methods (like GET, SET, etc) but it does not work with e.g. HSET or HGETALL.

If I look into type suggestions, I see the critical methods are actually not methods at all, but rather properties (hset, HSET):

Why is this so? How can I access those needed methods?

I guess I am doing something obvious wrong. Any ideas?

Edit: After thinking about the issue, the real question is what is an example of connecting to digitalocean's managed redis with node-redis using tls?

I'm able to connect just fine with redisinsight GUI client using username / password, but cannot connect with nodejs. It's on the same computer so no firewall issues.

Context: I am building an application that will be accessed concurrently by 1000 users and using Redis as the database. I am using node-redis client. I read that it's recommended to have only one or few connections open from each instance of the application because opening connections is expensive.

Question: Suppose the client sends a command to Redis. This command is in transit to Redis or being executed (essentially, not completed) when the application needs to send another command. Does the client wait for the first command to be completed or does it fire the second command to Redis right then?

This is important because if the client waits, the application is not really able to make full use of async and the network calls will become a big bottleneck when commands from a thousand users are trying to access Redis. It's better that the commands are queued up in Redis already instead of having them wait for an earlier command to complete before going through the network.

Thanks!

Wondering if anyone could help me out with this, as I'm new to NestJS.

I'm trying to use Redis in my existing NestJS service, rather than creating a separate microservice like Nest documents in their examples. When I import redis from node-redis it comes back as undefined.

token.service.ts

I have one redis client for pub-sub. I'm using a websocket message handler to dynamically subscribe to a redis channel. The payload of the websocket message contains an ID that I use to create the channel-name. So for example lobby:${lobbyID}:joined. Subscribing to this channel works fine, messages are received when publishing to that channel.

But the issue that I'm having is that I want to unsubscribe from this channel at one point. My assumption by reading the redis-documentation is that I would use punsubscribe so I can unsubscribe from any channels with the pattern lobby:*:joined, but messages are still received after trying that.