The motive of this post is to discuss how to design an application written in Node.js in a scalable fashion. On a wider scope, these principles apply to any event driven programming language. I’ll discuss where we went wrong in an Walmart’s internal application using a similar analogy.

I will discuss some points here which I noticed first-hand and think that make a difference in the life of a Software Engineer

The first question is what exactly are skip lists? I’ll suggest you to refer to this page to see what are skip lists. I’ll focus more on why and when are they important and better than binary search trees.

In college, there’s a class known as Data Structures. But what they teach you is just the same old trivial data structures. The best you might have heard of are segment trees, interval trees, suffix trees. There are a lot of interesting but less used data structures which you might want to know out of curiosity. Here are a few of them:

• Quadtrees
• Bloom filters
• Suffix trie
• Ropes
• Skip lists
• HyperLogLog
• Count-Min Sketch
• Zippers
• Spatial indexes
• etc etc.

Transition from college to Corporate life is a big change in all aspects, be it technology, atmosphere, culture, people etc. In this post, I will try to describe the basic technical terminology in terms a layman will understand. The examples might not only do the work mentioned in the tool description but a major usage will involve the functionality described.

One of the main problems which I encountered while writing Node.js applications in Walmart Labs is Memory Leaks.