Speed Up Your APIs with Nodejs and Redis Magic!

Поделиться
HTML-код
  • Опубликовано: 31 июл 2024
  • Speed Up Your APIs with Nodejs and Redis Magic
    This video'll delve into how to speed up API using redis. Lets increase your API performance.
    In this video, we have discussed how you build fast APIs that meet industry standards and user expectations.
    00:00 - Intro
    01:25 - What is Redis?
    02:29 - Example when and how Redis works?
    08:55 - Bonus use case of Redis in industry
    10:19 - Install redis
    12:23 - Code API with Redis
    #redis
    #nodejs
    #speedapi
    #apidesign
    #apidevelopment
    #bestpractices
    #api
  • НаукаНаука

Комментарии • 90

  • @sarthak_nande
    @sarthak_nande 20 дней назад +2

    best video I ever saw
    Thanks for this knowledge

  • @osama-ki_masi-ki_pota7677
    @osama-ki_masi-ki_pota7677 День назад

    Bhai apka padhane ka style mast aur simple hai

  • @Bhide.Svelte
    @Bhide.Svelte 16 дней назад +1

    bro you are god really i love it ...best explanation my friend, made by day

  • @funcreations4864
    @funcreations4864 12 дней назад +2

    Kon kon drop servicing wali didi ka ad dekha hai is video ko dekhne se pehle like here 😂😂

  • @jaydeep7932
    @jaydeep7932 20 дней назад +1

    great work bro 🤟

  • @RakeshSingh-vl2mz
    @RakeshSingh-vl2mz 14 дней назад +1

    Thanks bro learnt alot

  • @harshhrathore
    @harshhrathore 17 дней назад +1

    great video!!

  • @ganeshgajelly
    @ganeshgajelly 11 дней назад +1

    Amazing video.

  • @rushikeshbhumkar8474
    @rushikeshbhumkar8474 18 дней назад +1

    thank you

  • @tejassankhla1264
    @tejassankhla1264 22 дня назад +1

    Thanks much needed videos like these

  • @TrendingShorts-5G
    @TrendingShorts-5G 21 день назад +3

    Really amazing video on docker and redis please if possible make more on docker and redis please bhaiya . Your explanation is very good 🤩

    • @sandeepdev0
      @sandeepdev0  20 дней назад +1

      noted✅, content coming soon

  • @rushikeshbhumkar8474
    @rushikeshbhumkar8474 18 дней назад +1

    super brooo

  • @typesoffun
    @typesoffun 22 дня назад +1

    Keep it up bro ❤..

  • @ffgamer4140
    @ffgamer4140 22 дня назад +1

    Thank you very much😭 bro i really need this 😘

    • @sandeepdev0
      @sandeepdev0  22 дня назад

      Glad I could help😊 , it made my day

  • @user-by6oe1jl9j
    @user-by6oe1jl9j 16 дней назад +1

    Recently i have found you. your all videos are amazing sir, please bring a microservice video on node js with aws it will be so helpful. thanks.

    • @sandeepdev0
      @sandeepdev0  16 дней назад

      Noted✅, will bring this content very soon

  • @ranjeetchoudhary8820
    @ranjeetchoudhary8820 10 дней назад +1

    Hello Sir,
    Could you please upload a video tutorial where you create an eCommerce REST API similar to Walmart using Node.js, Redis, and Express.js? The tutorial should cover authentication and all other key points typically followed by the industry.

    • @sandeepdev0
      @sandeepdev0  10 дней назад +1

      Actually good Idea, Will do work on this soon

  • @Superuser-r1y
    @Superuser-r1y 15 дней назад +2

    Razorpay ka use krke nodejs me subscription api bano. 🙏

    • @sandeepdev0
      @sandeepdev0  15 дней назад

      Working on it bro✅, Next video will be on this and coming in just couple of days

  • @flutterdeveloper
    @flutterdeveloper 7 дней назад

    I think client side caching is better using next js or react query

  • @disharadadiya11
    @disharadadiya11 17 дней назад +3

    Please make a video on the payment gateway with node js please

    • @sandeepdev0
      @sandeepdev0  17 дней назад +1

      Noted✅, video will come soon on this topic

  • @flutterdeveloper
    @flutterdeveloper 7 дней назад +1

    But i guess there has to be some mechanism to invalidate the data after sometime manually

    • @sandeepdev0
      @sandeepdev0  7 дней назад

      there is TTL in Redis which will invalidate the data after fixed time which we set,
      But there are some other really great approaches in Redis like:
      1. Event Driven approach
      2. Polling
      3. Invalidation on updation of data
      4. Hybrid approaches

  • @ayushgandhi577
    @ayushgandhi577 16 дней назад +2

    I like your video but I'm looking for advanced projects
    For example - project-based on node.js typescript mongodb redis aws

    • @sandeepdev0
      @sandeepdev0  16 дней назад +1

      Advanced Full stack project tutorials - 1 shot videos coming soon

  • @NomiChak
    @NomiChak 13 дней назад

    How about use redis on cpanel?

  • @Superuser-r1y
    @Superuser-r1y 15 дней назад +2

    New sub❤👍

    • @sandeepdev0
      @sandeepdev0  15 дней назад

      welcome in the community bro💓

  • @DivineVibesHindus
    @DivineVibesHindus 14 часов назад

    how to check if data is changed

  • @JatinGupta-ze6nc
    @JatinGupta-ze6nc 17 дней назад +1

    guruji kha the ap apkw charan kha hai mai kitna darta tha ye soch k kya hai ye aj smjh aya

    • @sandeepdev0
      @sandeepdev0  16 дней назад

      I'm really glad that you have liked this video. One of the best comment on my channel ever😅,
      Also comment down on what topics you want the next videos on☺️

  • @Paper_Mastery
    @Paper_Mastery 20 дней назад +11

    one qustion well i can literally do that redies query but how will system know that user has updated query

    • @sarthaksingh6953
      @sarthaksingh6953 18 дней назад

      With the help of cdc

    • @sandeepdev0
      @sandeepdev0  17 дней назад +12

      Good question,
      Here is the detailed answer of your question on How to ensure Redis cache has most updated data
      1. Cache Invalidation on Update
      Whenever data is updated in the database, immediately invalidate or update the corresponding cache entry.
      Implementation Steps:
      Update the Database: Perform the update operation on the database.
      Invalidate Cache: Remove or update the relevant key in Redis.
      Example in Node.js:
      const redisClient = require('./redisClient'); // assuming you've set up your Redis client
      const db = require('./databaseClient'); // your database client
      async function updateData(id, newData) {
      // Update the database
      await db.update(id, newData);
      // Invalidate the cache
      await redisClient.del(`data:${id}`);
      }
      async function getData(id) {
      // Check the cache first
      let cachedData = await redisClient.get(`data:${id}`);
      if (cachedData) {
      return JSON.parse(cachedData);
      }
      // If not in cache, fetch from the database
      let data = await db.get(id);
      // Store in cache for future requests
      await redisClient.set(`data:${id}`, JSON.stringify(data));
      return data;
      }
      2. Write-Through Cache
      When updating data, write the new data to both the database and the cache simultaneously.
      Example in Node.js:
      async function updateData(id, newData) {
      // Update the database
      await db.update(id, newData);
      // Update the cache
      await redisClient.set(`data:${id}`, JSON.stringify(newData));
      }
      3. Cache with Expiry (TTL)
      Set a time-to-live (TTL) for cache entries. This ensures that even if cache invalidation is missed, the stale data will eventually expire and be refreshed from the database.
      Example in Node.js:
      async function getData(id) {
      let cachedData = await redisClient.get(`data:${id}`);
      if (cachedData) {
      return JSON.parse(cachedData);
      }
      let data = await db.get(id);
      // Store data with an expiry time (e.g., 60 seconds)
      await redisClient.setex(`data:${id}`, 60, JSON.stringify(data));
      return data;
      }
      4. Event-Driven Cache Invalidation
      Use events to trigger cache invalidation. Whenever the database updates, it emits an event that listeners (like the cache layer) can act upon.
      Example with Event Emitters:
      const EventEmitter = require('events');
      const cacheInvalidationEmitter = new EventEmitter();
      cacheInvalidationEmitter.on('dataUpdated', async (id) => {
      await redisClient.del(`data:${id}`);
      });
      async function updateData(id, newData) {
      await db.update(id, newData);
      cacheInvalidationEmitter.emit('dataUpdated', id);
      }
      By using one or a combination of these strategies, you can ensure that your Redis cache reflects the latest data from your database.
      Hope this answer will resolve your query, if not? feel free to ask here again and I will make a proper practical video on your boubt and will ensure you will get a proper answer😊

    • @iUmerFarooq
      @iUmerFarooq 15 дней назад +2

      @@sandeepdev0 Bhai mera be same he question tha. Ap es pher ek video he bana do Part2.
      Shukriya

    • @gangitlaraju9322
      @gangitlaraju9322 15 дней назад +1

      Need video

    • @Paper_Mastery
      @Paper_Mastery 13 дней назад

      @@sandeepdev0 nice 🙂 very soon I will be asking some more but currently little busy at ts learning

  • @vammotv5183
    @vammotv5183 18 дней назад +1

    This video got me to subscribed, amazing content and I have a question how much data I can store on redis? and also Instagram where storing cashed data

    • @sandeepdev0
      @sandeepdev0  18 дней назад +1

      Hey vammotv, first of all thanks for subscribing and joining our valuable community. Here is the short answer of your questions:
      How Much Data Can You Store in Redis?
      The amount of data you can store in Redis is limited by the available RAM on your server. For larger datasets, Redis Cluster allows sharding across multiple nodes to increase capacity.
      Also Redis provides various data structure which can be used for efficient data storing
      Instagram's Caching Strategy
      Although Instagram's real architecture isn't public fully, But through my research I got top know Instagram uses in-memory caches like Redis and Memcached for frequently accessed data, and CDNs for static assets. They also optimize databases and use a microservices architecture to handle large-scale data efficiently.
      Hope these answers were able to resolve your queries, if not? feel free to ask here again and I will try my best to make video on your questions and answer them propely and in-depth😊

    • @vammotv5183
      @vammotv5183 18 дней назад +1

      @@sandeepdev0 Please tell me how can I write like this and you know every linkedin post they are posting like this and I am unable to write like this and I search a lot and last I am unable to find how can I write content on post plz make a detailed video and I will share lot of my friends and please explain in detail, please make video ASAP

  • @vammotv5183
    @vammotv5183 15 дней назад +1

    Please tell me how can I write like this and you know every linkedin post they are posting like this and I am unable to write like this and I search a lot and last I am unable to find how can I write content on post plz make a detailed video and I will share lot of my friends and please explain in detail, please make video ASAP

    • @sandeepdev0
      @sandeepdev0  15 дней назад

      Hey bro, first of all, thanks for commenting, but sorry I didn't get your query, Can you explain to me a bit more and with clarity what you are exactly asking?

  • @HelooAapKaun
    @HelooAapKaun 22 дня назад +1

    nice video , btw which vs code extension u use that autocompletes ur code ??

    • @ffgamer4140
      @ffgamer4140 22 дня назад +1

      codium ai

    • @sandeepdev0
      @sandeepdev0  22 дня назад +1

      Actually I use github copilot, but if you want same or better for absolutely free you can go for codium ai

  • @shantanunimkar4471
    @shantanunimkar4471 18 дней назад +1

    Really amazing video bro , but I have a question, how can I ensure that when data is updated in the database, subsequent requests to the same route do not return stale data from Redis cache but instead fetch the updated data from the database?

    • @sandeepdev0
      @sandeepdev0  17 дней назад +2

      Good question,
      Here is the detailed answer on how you can ensure Redis always have updated data from database:
      👇👇
      There are various techniques like:
      1. Cache Invalidation on Update
      Whenever data is updated in the database, immediately invalidate or update the corresponding cache entry.
      Implementation Steps:
      Update the Database: Perform the update operation on the database.
      Invalidate Cache: Remove or update the relevant key in Redis.
      Example in Node.js:
      javascript
      const redisClient = require('./redisClient'); // assuming you've set up your Redis client
      const db = require('./databaseClient'); // your database client
      async function updateData(id, newData) {
      // Update the database
      await db.update(id, newData);
      // Invalidate the cache
      await redisClient.del(`data:${id}`);
      }
      async function getData(id) {
      // Check the cache first
      let cachedData = await redisClient.get(`data:${id}`);
      if (cachedData) {
      return JSON.parse(cachedData);
      }
      // If not in cache, fetch from the database
      let data = await db.get(id);
      // Store in cache for future requests
      await redisClient.set(`data:${id}`, JSON.stringify(data));
      return data;
      }
      2. Write-Through Cache
      When updating data, write the new data to both the database and the cache simultaneously.
      Example in Node.js:
      async function updateData(id, newData) {
      // Update the database
      await db.update(id, newData);
      // Update the cache
      await redisClient.set(`data:${id}`, JSON.stringify(newData));
      }
      3. Cache with Expiry (TTL)
      Set a time-to-live (TTL) for cache entries. This ensures that even if cache invalidation is missed, the stale data will eventually expire and be refreshed from the database.
      Example in Node.js:
      async function getData(id) {
      let cachedData = await redisClient.get(`data:${id}`);
      if (cachedData) {
      return JSON.parse(cachedData);
      }
      let data = await db.get(id);
      // Store data with an expiry time (e.g., 60 seconds)
      await redisClient.setex(`data:${id}`, 60, JSON.stringify(data));
      return data;
      }
      4. Event-Driven Cache Invalidation
      Use events to trigger cache invalidation. Whenever the database updates, it emits an event that listeners (like the cache layer) can act upon.
      Example with Event Emitters:
      const EventEmitter = require('events');
      const cacheInvalidationEmitter = new EventEmitter();
      cacheInvalidationEmitter.on('dataUpdated', async (id) => {
      await redisClient.del(`data:${id}`);
      });
      async function updateData(id, newData) {
      await db.update(id, newData);
      cacheInvalidationEmitter.emit('dataUpdated', id);
      }
      By using one or a combination of these strategies, you can ensure that your Redis cache reflects the latest data from your database.
      I hope this answer will resolve your query, if not? feel free to ask in comments section and I will make dedicated video on this topic and practically explain you how you can ensure Redis cache have most updated data

    • @sandeepdev0
      @sandeepdev0  17 дней назад +1

      Good question,
      Here is the detailed answer of your question on How to ensure Redis cache has most updated data
      1. Cache Invalidation on Update
      Whenever data is updated in the database, immediately invalidate or update the corresponding cache entry.
      Implementation Steps:
      Update the Database: Perform the update operation on the database.
      Invalidate Cache: Remove or update the relevant key in Redis.
      Example in Node.js:
      const redisClient = require('./redisClient'); // assuming you've set up your Redis client
      const db = require('./databaseClient'); // your database client
      async function updateData(id, newData) {
      // Update the database
      await db.update(id, newData);
      // Invalidate the cache
      await redisClient.del(`data:${id}`);
      }
      async function getData(id) {
      // Check the cache first
      let cachedData = await redisClient.get(`data:${id}`);
      if (cachedData) {
      return JSON.parse(cachedData);
      }
      // If not in cache, fetch from the database
      let data = await db.get(id);
      // Store in cache for future requests
      await redisClient.set(`data:${id}`, JSON.stringify(data));
      return data;
      }
      2. Write-Through Cache
      When updating data, write the new data to both the database and the cache simultaneously.
      Example in Node.js:
      async function updateData(id, newData) {
      // Update the database
      await db.update(id, newData);
      // Update the cache
      await redisClient.set(`data:${id}`, JSON.stringify(newData));
      }
      3. Cache with Expiry (TTL)
      Set a time-to-live (TTL) for cache entries. This ensures that even if cache invalidation is missed, the stale data will eventually expire and be refreshed from the database.
      Example in Node.js:
      async function getData(id) {
      let cachedData = await redisClient.get(`data:${id}`);
      if (cachedData) {
      return JSON.parse(cachedData);
      }
      let data = await db.get(id);
      // Store data with an expiry time (e.g., 60 seconds)
      await redisClient.setex(`data:${id}`, 60, JSON.stringify(data));
      return data;
      }
      4. Event-Driven Cache Invalidation
      Use events to trigger cache invalidation. Whenever the database updates, it emits an event that listeners (like the cache layer) can act upon.
      Example with Event Emitters:
      const EventEmitter = require('events');
      const cacheInvalidationEmitter = new EventEmitter();
      cacheInvalidationEmitter.on('dataUpdated', async (id) => {
      await redisClient.del(`data:${id}`);
      });
      async function updateData(id, newData) {
      await db.update(id, newData);
      cacheInvalidationEmitter.emit('dataUpdated', id);
      }
      By using one or a combination of these strategies, you can ensure that your Redis cache reflects the latest data from your database.
      Hope this answer will resolve your query, if not? feel free to ask here again and I will make a proper practical video on your boubt and will ensure you will get a proper answer😊

    • @shantanunimkar4471
      @shantanunimkar4471 16 дней назад

      @@sandeepdev0 Thank you 😁

  • @AyushGupta-ux4gq
    @AyushGupta-ux4gq 19 дней назад +2

    isn't similar to memoisation concept ?

    • @sandeepdev0
      @sandeepdev0  18 дней назад

      Yes Ayush, you are absolutely right ✅

  • @LOLlol-kw5fo
    @LOLlol-kw5fo 18 дней назад +1

    What about accounting software there data needs to be real-time

    • @sandeepdev0
      @sandeepdev0  17 дней назад

      Redis Pub/Sub can be used in these types of softwares

  • @swapnilpatel3337
    @swapnilpatel3337 21 день назад

    Schema to diffrence hogi jab ki microservice pe kam karta he instagram to db bhi alg he

    • @sandeepdev0
      @sandeepdev0  21 день назад +1

      yes you are right, but I also said that this is just an example and its not the actual and real architecture of Instagram. That was just a simple example to make everyone understand the problem solved by Redis.

    • @sandeepdev0
      @sandeepdev0  21 день назад +1

      But thanks for commenting on the video☺️

    • @swapnilpatel3337
      @swapnilpatel3337 20 дней назад +1

      @sandeepdev0 thank you sir...

  • @wasimzaman674
    @wasimzaman674 14 дней назад

    Different APIs k liye different caching Karne se Radis ki wajah se memory leak nahi hogi ?

    • @sandeepdev0
      @sandeepdev0  14 дней назад

      When using Redis, it is crucial to follow best practices to ensure there are no memory leaks:
      1. Use the LRU eviction policy to automatically remove the least recently used entries when memory limits are reached.
      2. Set TTL (Time-to-Live) for each cache entry to automatically remove stale data.
      3. Set memory limits to prevent Redis from consuming excessive memory.
      4. Implement cache segmentation to manage memory usage more effectively by using distinct keys for different APIs.
      5. And make sure to use effective data structure according to your system/data need, because Redis supports a variety of data structures to manage data effectively.

  • @anuragsidhu7863
    @anuragsidhu7863 19 дней назад +2

    In production how its going to work . When i stop docker , redis will not work .

    • @sandeepdev0
      @sandeepdev0  19 дней назад

      In production, There are various ways, like you can use Redis cloud, where Redis is hosted on the cloud or you can host Redis on your server as well, for example on AWS EC2 using the same docker image, and also AWS, Azure, etc. (famous cloud providers) provides Redis cloud in their services which are usually used in production.
      Hope this answer has resolved your query if not? feel free to ask in the comments section

    • @anuragsidhu7863
      @anuragsidhu7863 19 дней назад

      How about upstash . For production

    • @anuragsidhu7863
      @anuragsidhu7863 19 дней назад +1

      @@sandeepdev0 ​ How about upstash for production

    • @sandeepdev0
      @sandeepdev0  17 дней назад

      Yes, upstash also can be used in production. Its also great👌

    • @anuragsidhu7863
      @anuragsidhu7863 17 дней назад

      @@sandeepdev0 thanks 👍

  • @jayantgupta5310
    @jayantgupta5310 16 дней назад +1

    Bhai ye thoda music dhang ka use kiya kr, baki sb theek hai

    • @sandeepdev0
      @sandeepdev0  16 дней назад

      Got it bro, I will be careful next time☺️

  • @rnp0728
    @rnp0728 15 дней назад +1

    What if my data comes from database and it changes continuously?

    • @rnp0728
      @rnp0728 15 дней назад +1

      Atleast reply don't just like the comments

    • @sandeepdev0
      @sandeepdev0  15 дней назад +1

      If your data changes continuously, you need a robust caching strategy to ensure data consistency while minimizing the performance impact. Here are some approaches:
      1. Event-Driven Updates
      Emit events on data changes and have the cache update itself based on those events.
      Example with Event Emitters:
      const EventEmitter = require('events');
      const cacheUpdateEmitter = new EventEmitter();
      cacheUpdateEmitter.on('dataUpdated', async (id, newData) => {
      await redisClient.set(`data:${id}`, JSON.stringify(newData));
      });
      async function updateData(id, newData) {
      await db.update(id, newData);
      cacheUpdateEmitter.emit('dataUpdated', id, newData);
      }
      2. Polling
      Periodically poll the database for changes and update the cache accordingly.
      Example:
      async function pollAndUpdateCache(id) {
      setInterval(async () => {
      let data = await db.get(id);
      await redisClient.set(`data:${id}`, JSON.stringify(data));
      }, 5000); // Poll every 5 seconds
      }
      5. Hybrid Approach
      Combine several strategies for optimal performance and consistency.
      By implementing one or a combination of these strategies, you can handle continuously changing data effectively while maintaining cache consistency.

    • @sandeepdev0
      @sandeepdev0  15 дней назад +1

      In some cases like Chat Apps where messages are sent in realtime , you can utilize Redis Pub Sub for optimize the performance

    • @sandeepdev0
      @sandeepdev0  15 дней назад +1

      Sorry bro for late replying, thanks for waiting, here I have given the answer, but if you still have more questions, want more clarity upon answers, feel free to comment here, I will make a dedicated practical video for resolving your queries😊

    • @rnp0728
      @rnp0728 15 дней назад +1

      @@sandeepdev0 thanks, will try to implement once, then I will get back to you

  • @vammotv5183
    @vammotv5183 14 дней назад

    Bro, see my comments you can understand what I am telling

  • @JourneyOfCricket
    @JourneyOfCricket 17 дней назад +3

    But if we want real-time data then?

    • @sandeepdev0
      @sandeepdev0  17 дней назад

      REDIS PUB SUB can be used in this case

    • @JourneyOfCricket
      @JourneyOfCricket 17 дней назад

      @@sandeepdev0 can you create video on that

    • @JourneyOfCricket
      @JourneyOfCricket 17 дней назад

      @@sandeepdev0 thanks

    • @JourneyOfCricket
      @JourneyOfCricket 17 дней назад

      And if there is any change on data in that case ?

    • @nasarali5186
      @nasarali5186 15 дней назад

      ​@@sandeepdev0What about sockets