{"id":1302,"date":"2016-06-12T14:50:23","date_gmt":"2016-06-12T09:20:23","guid":{"rendered":"http:\/\/code.ciphertrick.com\/?p=1302"},"modified":"2016-06-12T14:50:23","modified_gmt":"2016-06-12T09:20:23","slug":"avoiding-callback-hell-node-js","status":"publish","type":"post","link":"https:\/\/thrivemyway.com\/avoiding-callback-hell-node-js\/","title":{"rendered":"Avoiding callback hell in Node.js"},"content":{"rendered":"\n

Callback hell<\/b> is a phenomenon that afflicts a JavaScript developer when he tries to execute multiple asynchronous operations one after the other. Some people call it to be the pyramid of doom<\/b>.
\nLet’s have a look at an example of what we call callback hell.<\/p>\n\n\n\n


\ndoSomething(param1, param2, function(err, paramx){
\n doMore(paramx, function(err, result){
\n insertRow(result, function(err){
\n yetAnotherOperation(someparameter, function(s){
\n somethingElse(function(x){
\n });
\n });
\n });
\n });
\n});
\n<\/code><\/p>\n\n\n\n

Note-<\/b> The above code is for demonstration and not a working code.<\/p>\n\n\n\n

This is looking bad just from the skeleton itself. In real code you will obviously have other statements like if<\/kbd>, for<\/kbd> or some other operations along with these nested functions. Add those to the above code and it would get really messy and unmanageable.<\/p>\n\n\n\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n