Streams are accumulations of information — simply like clusters or strings. What matters is that streams PROBABLY won't be accessible at the same time, and they don't need to fit in memory. This makes streams extremely amazing when working with a lot of information, or information that is originating from an outer source one piece at once.  

Notwithstanding, streams are not just about working with enormous information. They additionally give US the intensity of composability in our code. MUCH the same as we can create ground-breaking linux directions by funneling other littler Linux directions, we can do precisely the equivalent in Node with streams. 

Streams are extraordinary kinds of objects in Node that enable us to peruse data from a source or compose data to a goal consistently. There are 4 kinds of streams accessible in Node Js, they are  

• Comprehensible − For perusing task.  
• Writable − For COMPOSING task.  
• Duplex − Used for both read and compose task.  
• Change − A kind of duplex stream where the yield is figured DEPENDENT on the information.