Optimizing API Performance with NodeCache in Node.js

-

 

Introduction : 

Efficient API response time is crucial for any web application. One way to achieve this is by implementing caching. In this blog, we'll explore how NodeCache can be used in a Node.js project to improve performance by reducing redundant API calls

What is Caching?

Caching stores frequently accessed data in memory, allowing for quicker retrieval. Instead of fetching data repeatedly from an external API or database, the system first checks if the required data is already available in cache

Why Use NodeCache?

  • Improves response time by avoiding repeated API calls

  • Reduces API rate limits and dependency on external services

  • Enhances scalability by lowering server load





                                       fig1: CACHING IN NODE.JS
                                                         

How to Implement NodeCache in Node.js

Step 1: Install NodeCache

   npm install node-cache

Step 2: Import and Configure NodeCache

  • const NodeCache = require("node-cache");
  • const cache = new NodeCache({ stdTTL: 60, checkperiod: 120 });

  • stdTTL: Standard time-to-live (TTL) in seconds

  • checkperiod: Interval to remove expired cache data

Node-cache has following major functions


  • .set(key, val, [ ttl ]): Used to set some value corresponding to a particular key in the cache. This same key must be used to retrieve this value.
  • .get(key):Used to get value set to specified key. It returns undefined, if the key is not already present.
  • has(key): Used to check if the cache already has some value set for specified key. Returns true if present otherwise false.

Working of node-cache 

first request 

                                      


Whenever a request (GET/products) is made, it will check whether data is available in the cache to that specified key (products) using has (key) method. If it is not available, it will fetch data from the fake API database and store it in the cache using the set (key, value) method.

Second Request

                     
                                        


From the next request onwards, it will check whether data is available in the cache to that specified key(products) using has (key) method. If it's available, it will get the data from the cache directly using the get (key) method.

Conclusion

Using NodeCache improves performance, reduces API load, and enhances user experience. By integrating caching, we ensure optimal API usage and avoid unnecessary requests.



Recommended Articles 

  1. https://infinijith.com/blog/nodejs/node-cache
  2.    Advantages of using microservices in Nodejs
  3. Optimizing app performance with Nodejs cluster


                                

Comments

Post a Comment

Popular posts from this blog

What Is a Proxy? A Simple Explanation for Beginners

-
Image
  Understanding Proxies – The Simplest Way I Learned It When I first heard the word proxy , I just thought — "Okay, it’s some kind of middleware between me and the server." But I didn’t really understand how it works, or why it's used. Now after deep diving, here’s how I understood it — and I’m writing this blog for anyone like me who just wants a simple explanation. The Basic Idea of a Proxy :  When you request something from the internet — like visiting google.com — you usually think your device talks directly to Google. But with a proxy , your request first goes to the proxy server , and then the proxy sends it to Google. The response comes back to the proxy, and then it sends it to you. So the proxy is standing between you and the actual server Real-Life Analogy: Your Home Wi-Fi Router :       Let me explain using my home Wi-Fi example: When I connect to my home router, it gives me a private IP like 192.168.x.x . But the internet doesn’t rec...
Read more

How to Implement API Rate Limiting in a NodeJS Express Application

-
Image
  What is Rate Limiting?    Rate Limiting is a "protection shield" that you place between incoming requests and your controller logic. It helps prevent abuse, brute-force attacks, and traffic spikes by controlling how frequently clients can hit your API. Rate limiting is a technique used to control the number of requests a client can make to a server within a specific time frame. It prevents: DDoS attacks Brute-force login attempts API overuse by a single user Unintentional client bugs flooding your server In short, it's like a bouncer for your serve r fig1 . Rate-limit 🤔 Why Use Rate Limiting? Here’s why it matters: 🔒 Security : Blocks malicious actors trying to overload your endpoints. ⚖️ Fair Usage : Ensures no single user hogs the API. 💸 Cost Control : Reduces unnecessary server usage (especially important with cloud billing). 🧘 Stability : Maintains smooth performance under high traffic. ⚙️ Rate Limiting Algorithms    ...
Read more