That's so great to hear! Make sure to check out Guy Royse's livestreams as well, he writes everything in JS and is always entertaining. You should also check out our Redis University course integrating Redis with JS here: university.redis.com/courses/ru102js/ Best of luck! - Justin
Great video. I had a problem at first with 'process.env.WEATHER_API_KEY'. I ended up viewing other RU-vid videos to figure out that I needed to set up a system environment variable. I am new to NodeJS
Thanks, Phil! I should have added a comment in the code to explain that better. I'll add that now. Welcome to the wild, wacky world of Node.js! - Justin
Exactly. Today I tried SISMEMBER with redis enterprise cloud the response is only a 1 / 0 the time it took was between 78ms and 14ms. That's time added to my api response. So imagine something more heavy 🤔
@@privymassage3458 you'd want to run your code as close as possible to the database to minimize round trip latency. Using Redis Cloud you can choose between AWS, Azure and GCP and pick the same or closest region to where you run your applications to achieve this.
how is your redis docker config? are you using docker desktop? i try to do this but does not seem the redis instance is visible outside the container, trying to figure out how docker desktop does the mapping basically
This is the command I use to start up a Redis-Stack image with RedisInsight. It exposes the Redis default port (6379) and the browser access to Redis Insight (8001): docker run -d --name redis-stack -p 6379:6379 -p 8001:8001 redis/redis-stack:latest Here's our page on the different configurations. Hope this helps! - Justin
I got this error after importing ioredis : This dependency was not found: * dns in ./node_modules/ioredis/built/cluster/ClusterOptions.js To install it, you can run: npm install --save dns
Glad you enjoyed the video! We don't really do zoom meetings, but you can join our discord channel at discord.gg/redis and we should be able to assist. - Justin
During setting and getting key into redis we need to JSON parse and stringify the large object and that creates performance issue so how to overcome with that issue
With Redis in the cloud, all of the applications would hit the same Redis instance. The first time an app instance hits a query and saves the result in the cache, other subsequent instances would check the Redis cloud and use that result until the TTL deletes that cache entry. Did that answer your question? - Justin
Justin. Lets take your great weather app as an example. Lets imagine we get update messages from our weather client telling us that the weather has changed rather than the 1hr TTL you did in the app and we want to pre warm the cache based on that message. Lets also imagine we want to be highly available so we have 2 instances of our weather app running in 2 different data centers. When both apps receive the update message from the weather center how do we stop contention in Redis? @@Redisinc
