{"id":34034,"date":"2016-04-30T20:21:52","date_gmt":"2016-04-30T14:51:52","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=34034"},"modified":"2016-12-19T15:02:53","modified_gmt":"2016-12-19T09:32:53","slug":"caching-in-nodejs-using-redis","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/caching-in-nodejs-using-redis\/","title":{"rendered":"Caching in NodeJs using Redis"},"content":{"rendered":"

Whenever we talk about nodejs development<\/a>, the first thing that comes to our mind is managing concurrent requests in an efficient way. We can leverage our server performance and efficiency even more by providing a mechanism to cache it’s processed data(response) which seldomly changes. Such as products list, country codes, application configurations, etc.<\/p>\n

In this blog, we will be using the Redis(an in-memory data store) to achieve caching in a node server. To begin with it, we will need redis to be installed on to our machine (link : .<\/p>\n

After installing redis to your machine we can start the redis server.<\/p>\n

\"redis\"<\/p>\n

The default port of redis is 6379. For more details about redis you can refer to http:\/\/redis.io\/.<\/p>\n

Let us consider an example where we have to fetch list of products from a legacy application server, and the list of products seldomly changes. So we can easily cache these products list on our nodejs server. To do so, we need to require the redis module in our node application, which serves as a redis client to connect with the redis server.<\/p>\n

[js]
\nvar redis = require(‘redis’);
\nvar client = redis.createClient(6379, ‘127.0.0.1’);
\n[\/js]<\/p>\n

Now we can use this client to store and fetch the data from the cache(redis).<\/p>\n

To store the value in redis:<\/p>\n

[js]
\nclient.set(<key>, JSON.stringify(<value>), function(error) { });
\n[\/js]<\/p>\n

And to fetch value from redis:<\/p>\n

[js]
\nclient.get(<key>, function(error, value) { });
\n[\/js]<\/p>\n

The below code demonstrates, how redis can be used with express framework(NodeJs)<\/p>\n

[js]
\nvar express = require(‘express’);
\nvar app = express();
\nvar bodyParser = require(‘body-parser’);
\nvar request = require(‘request’);<\/p>\n

var redis = require(‘redis’);
\nvar client = redis.createClient(6379, ‘127.0.0.1’);<\/p>\n

app.use(bodyParser.json());
\napp.use(bodyParser.urlencoded({
\n extended: true
\n}));<\/p>\n

app.get(‘\/products\/:id’, function (req, res) {
\n client.get(req.params.id, function(error, product) {
\n if (error) {throw error;}
\n if (product) {
\n res.json(JSON.parse(product));
\n } else {
\n request({uri: ‘<some_other_domain>\/products\/’ + req.params.id}, function(error, response, body) \t\t\t\t\t\t\t {
\n if (error) {throw error;return}
\n if (!error && response.statusCode === 200) {
\n res.json(body);
\n client.set(req.params.id, JSON.stringify(body), function (error) {
\n if (error) {throw error;}
\n });
\n } else {
\n res.send(response.statusCode);
\n }
\n });
\n }
\n });
\n });<\/p>\n

var server = app.listen(3000, function () {
\n console.log(‘Server running at ‘);
\n});[\/js]<\/p>\n

The products API first try to check the data in the redis, before fetching it from \u201csome_other_domain\u201d. If the data is present in redis then, it will fetch it from the memory and respond back to the request. Else it will make a request to the \u201csome_other_domain\u201d and then store the response to redis before responding back to the request, so that it can be cached.<\/p>\n

If you want to set an expiration time for the cache, you can do so by using the \u2018setex\u2019 method of redis module.<\/p>\n

Syntax:<\/p>\n

[js]
\nclient.setex(<key>, <expirationTimeInSeconds>, JSON.stringify(<value>), function (error) { });
\n[\/js]<\/p>\n

Similarly, we can also cache database result sets in redis, to enhance the performance of the APIs. By specifying expiration we can also take the advantage of refreshing our server cache as per the need of our application.<\/p>\n

To demonstrate the API performance, I fetched 5000 records from a different server. It took around 19 seconds to respond without caching. And after caching the data on our node server, it just took around 110 millisecond to respond back.<\/p>\n

Without Caching the response from our server:
\n\"without<\/p>\n

Server response, after caching the request on Redis:
\n\"after<\/p>\n

This difference is self explanatory, to understand the power of caching with redis.<\/p>\n

Hope this will help. Happy coding.<\/p>\n","protected":false},"excerpt":{"rendered":"

Whenever we talk about nodejs development, the first thing that comes to our mind is managing concurrent requests in an efficient way. We can leverage our server performance and efficiency even more by providing a mechanism to cache it’s processed data(response) which seldomly changes. Such as products list, country codes, application configurations, etc. In this […]<\/p>\n","protected":false},"author":99,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":4},"categories":[1185,1],"tags":[1072,3284,55,1177,2683,857],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/34034"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/99"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=34034"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/34034\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=34034"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=34034"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=34034"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}