How streams can simplify your life
Tags: rxjs, reactiveprogramming, javascript
Published: 2019-07-08 18:51:48

---
title: How streams can simplify your life
published: true
tags: rxjs,reactive-programming,javascript
canonical_url: https://blog.logrocket.com/how-streams-can-simplify-your-life-494a4b247f36
---

![](https://cdn-images-1.medium.com/max/1024/1*6pOf7I0d_iD-lqKDgK2jRQ.png)

In the land of web development, **streams** (and their building blocks, **observables** ) are an increasingly popular topic. Libraries like [BaconJS](https://baconjs.github.io/) and [RxJS](https://rxjs.dev/guide/overview) have been around for years now, and RxJS is even [used as a foundation for Angular 2+](https://auth0.com/blog/making-use-of-rxjs-angular/). In fact, there’s even a TC39 proposal to add [native observables](https://github.com/tc39/proposal-observable) to the language.

So streams are kind of a big deal. But… why? Why do so many people care about streams?

The short answer is that a stream-based approach dramatically simplifies several problems that have caused migraines for decades. We’ll talk about those problems and how streams help to solve them in a sec, but before we do, I want to plant a seed here, present an overall theme that I want you to keep in the back of your mind as we continue.

The problems that streams solve are all about **sending, receiving, and processing data.** So here’s our thematic seed: as I see them, what streams provide is a change of perspective from **asking for data** to **listening for data**.

[![](https://cdn-images-1.medium.com/max/1024/1*GPjaPKNNUYHU8EsA3Z0JGA.png)](https://logrocket.com/signup/)

### The problems

It’s nearly too obvious to be worth saying (but here I go) — modern web applications are _incredibly complex_. They tend to have a ton of more-or-less independent components all sitting on a page at the same time, requesting data from various sources, transforming that data, combining data from different sources in interesting ways, and ultimately, if all goes well, putting some of that data on the screen for us users to look at.

And by the way, “data source” doesn’t just mean “REST API”. Data can come from all sorts of places:

- Web socket connections for real-time updates from the server
- User input events, like mouse movements or keyboard events in a text field
- [Input from sensors](https://developer.mozilla.org/en-US/docs/Web/API/Sensor_APIs#Interfaces), like a phone’s gyroscope or accelerometer
- [postMessage()](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage) communications from web workers, iframes, or related windows
- Storage change events from [localStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage) or [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API)

And the list goes on (you can probably think of something I’ve missed).

All of this complexity can be tough to manage. Here are a few problem situations that come up all the time:

- A single data source is used simultaneously by several independent components
- A component needs to listen for updates from its data sources and react to them in real-time
- Several independent parts of an application need to be kept in sync; updates from a single data source should be reflected everywhere as instantly as possible
- User actions in one component should update several other independent components so that the one component acts as a data source for the others
- Each component uses a different set of data sources, combining their outputs in unique ways, often transforming and merging data from those sources to suit that component’s needs. This transformation needs to happen again after each update from any of its data sources

Streams can handle all of these problems with ease, and do so in a way that’s easy to follow and understand.

### What are streams?

Before we get into code samples, let’s talk a tiny bit of theory, just for a minute.

The software design pattern being invoked here is called [the Observer pattern](https://en.wikipedia.org/wiki/Observer_pattern). In this pattern, we’ve got two important players: “observers” and “subjects” (also called “observables”). As their names suggest, observers “observe” subjects, and whenever subjects emit any data, observers find out about it. In code, this is accomplished by subjects keeping a list of all observers that are currently observing them, and whenever they’ve got some data to pass along, they run through that list and call a special method on each observer, passing the data as an argument.

The observer pattern is used all over the place in software. It’s the basic architecture behind all pub/sub interactions. You can even think of everyday event handlers as observers. And I think it’s clear why this pattern is so popular: the ability to easily find out about asynchronous events when they happen, and to get data from a source whenever it’s available without needing to poll for it, is very powerful.

Streams are one layer of abstraction higher than observers and subjects. Streams use subjects that can also act as observers, observing other subjects to receive data. Each subject observes someone else to wait for data, performs some kind of processing on the data it receives, then sends some data along to whoever is observing it. These observer-subjects make it really easy to build up long chains of data processors that can do interesting things with the data and help get it to the components in our app that need it.

Another aspect worth mentioning is that just as a single subject can be observed by multiple observers, a single observer can also observe multiple subjects. This enables merging data from different sources together in all sorts of interesting ways.

Take a moment and imagine linking lots of these individual observer-subjects together, then step back and look at the big picture. Think about how data flows through this system from sources to destinations, merging with data from other sources, splitting into tributaries and joining up again with more data, creating interesting paths to bring it to where it’s needed all over our system very efficiently. This big picture is what we talk about as “streams”.

### The code examples

So now that we know the theory, let’s put it into practice.

For each data source you have, no matter what kind of source it is, create a subject and make it available to any component that needs data from that source. Different UI frameworks facilitate this in different ways, but for our purposes, we’ll put each subject in a JavaScript module. Then any component that needs data from that source can import the subject.

> **Note:** I’ll use JavaScript as the language and RxJS as the stream library for the code examples here, but this is arbitrary. RxJS is what I’m most familiar with, but there are other stream libraries that accomplish the same thing, both in JS and other languages. In fact, RxJS is just the JavaScript implementation of an abstract sort-of-spec called [ReactiveX](http://reactivex.io/) that has implementations in [all sorts of languages](http://reactivex.io/languages.html).

So suppose we need to poll an API periodically. We can create a subject to handle that, using RxJS’s handy ajax helper and the interval function, which creates a subject that emits at the specified interval. (The pipe operator essentially chains together the operators you give it, and switchMap creates a new observable from each bit of data it receives, then emits that observable’s data before creating the next one, but don’t get too hung up here; these are specific to RxJS and sort of beside the point).

<iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c3b25cc9a3e9a2923067ade5cbaacaa8/href">https://medium.com/media/c3b25cc9a3e9a2923067ade5cbaacaa8/href</a></iframe>

We can keep going this way, creating a module for each data source that returns a subject. When it’s time to use the data from these sources in a component, it’s as easy as any other import:

<iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1dc4022e957518ef13a79410a0ef1996/href">https://medium.com/media/1dc4022e957518ef13a79410a0ef1996/href</a></iframe>

This is already useful, to have all data sources producing data through a common interface. But the real power of streams comes from the incredible ease with which we can process and manipulate data by chaining together those observer-subjects. Stream libraries like RxJS make this very easy by providing “operator” methods on their subject data types that each internally observe the subject and return a new subject to be observed.

To demonstrate this, let’s imagine a very simple example: a chat room application. In this scenario, the above web socket could be used for real-time chat notifications, and the API could be used for updates from the server that don’t need to be quite as real time. (Yeah, I know, you could do both over web socket, but let’s roll with this for the sake of demonstration).

Suppose our server updates API returns two sorts of things:

- an updated list of who is on the server whenever the list changes
- occasional server notices that should appear in the chat room for all users to see

Suppose the packets received from the server are formatted this way:

<iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aeee755a101c124d2366e2b86ca48ce2/href">https://medium.com/media/aeee755a101c124d2366e2b86ca48ce2/href</a></iframe>

We need to handle the “who” messages by updating the user list, and handle the “notice” messages by displaying them in the chatroom. One way to accomplish the second task might be to treat the notices the same as user messages, and give them a special user name, like “SERVER”.

Now suppose that messages received from the web socket are formatted this way:

<iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5a2c2446e7d1771ea432787e9188ccdc/href">https://medium.com/media/5a2c2446e7d1771ea432787e9188ccdc/href</a></iframe>

We’ll need to transform notices to match this format and combine the notice messages with the web socket messages to send to the chatroom. Fortunately, with streams this is super simple:

<iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3bc39a5a4cb83608fa1d663efced273/href">https://medium.com/media/e3bc39a5a4cb83608fa1d663efced273/href</a></iframe>

Not bad at all! Something that’s not super obvious from this code, since it’s abstracted away behind fancy helpers and operators, is that every one of those helpers and operators (webSocket, ajax, from, pluck, switchMap, filter, merge) creates a new subject that observes the previous subject (or subjects!) in the stream, does something with each bit of data it receives and sends something new down the stream. The special subscribe method creates a simple observer that consumes whatever comes out the end of the stream, but can’t itself be observed.

### How streams solve our problems

So now that we’ve seen a little of what streams can do, let’s return to the list of problems we talked about earlier and make sure we have an answer to each of them. Let’s take them one-by-one:

- A single data source is used simultaneously by several independent components. — Wrapping your subject in a module will allow any component to get to it and subscribe to it
- A component needs to listen for updates from its data sources and react to them in real-time. — This is the whole idea of the Observer Pattern: as soon as a subject emits data, its observers find out about it and can react in real time
- Several independent parts of an application need to be kept in sync; updates from a single data source should be reflected everywhere as instantly as possible. — Multiple observers can observe the same subject, so keeping different components in sync is easy
- User actions in one component should update several other independent components so that the one component acts as a data source for the others. This one has a few possible solutions, depending on use case. One way that I have accomplished this in the past is to create a central module with a subject that represents the data source and allow components to both subscribe and push data to the subject. In RxJS, the Subject type has a method called “next” that can be called to hand some data to the subject:
<iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/57866a1d125e62c8c27c85181761e861/href">https://medium.com/media/57866a1d125e62c8c27c85181761e861/href</a></iframe>
- Each component uses a different set of data sources, combining their outputs in unique ways, often transforming and merging data from those sources to suit that component’s needs. This transformation needs to happen again after each update from any of its data sources. — We saw a simple example of this with combining the web socket messages and server notices into a single stream. Any time a message came in from either data source, it was immediately pushed into the chat room. This was a very simplistic example, but hopefully, you can see how you might extend it to handle more complex situations. RxJS has several functions besides just merge that deal with combining data from multiple streams, such as combineLatest, zip, or concat.

### Stuff I didn’t talk about

This was a relatively shallow dive into streams, but I hope I’ve managed to give a glimpse of the power streams can provide. They can significantly simplify the flow of data through a system, especially when dealing with several data sources that need to interact and update disparate parts of an application simultaneously.

But because I wanted this to stay pretty shallow, there’s a lot I didn’t talk about. How do you handle errors in the stream? How do you clean up your observables to prevent memory leaks? What the heck are “hot” and “cold” observables? All of these are super important and should be some of the first things you learn if you decide to dive into streams (heh), but that’s the part I was focusing on: convincing you to dive in. I hope I’ve done that!

### More resources

If you want to learn more about what streams can do for you, and I hope you do, here are some links for further reading/viewing:

- An overview of the operators provided by ReactiveX: [http://reactivex.io/documentation/operators.html](http://reactivex.io/documentation/operators.html). I have found that reading through the operators gives good insight into what streams can do for you. If you want something more interactive, the RxJS docs have an interactive “Choose your operator” guide here: [http://reactivex.io/rxjs/manual/overview.html#choose-an-operator](http://reactivex.io/rxjs/manual/overview.html#choose-an-operator)
- If there’s one person I would recommend following in order to learn about stream-based (he says “reactive”) programming, it’s [Ben Lesh](https://twitter.com/BenLesh). He’s done a ton of awesome talks on both RxJS and “reactive programming” in general, and his blog posts are super well written and informative as well. Here are some highlights:
- [Thinking Reactively](https://www.youtube.com/watch?v=3LKMwkuK0ZE) — a great talk on how to wrap your head around Observer-based architectures, and how to think about the problems you’re solving in “reactive” terms
- [Learning Observable by Building Observable](https://medium.com/@benlesh/learning-observable-by-building-observable-d5da57405d87) — A great blog post in which Ben introduces a mantra he often repeats: “Observables are just functions”. Definitely worth a read
- [Hot vs Cold Observables](https://medium.com/@benlesh/hot-vs-cold-observables-f8094ed53339) — One of the first questions to answer when you decide to dive in
- [The introduction to Reactive Programming you’ve been missing](https://gist.github.com/staltz/868e7e9bc2a7b8c1f754) — A great introduction to observables and streams by [André Staltz](https://twitter.com/andrestaltz) that gets a little more technical than I did here

### Plug: [LogRocket](https://logrocket.com/signup/), a DVR for web apps

[![](https://cdn-images-1.medium.com/max/1024/1*s_rMyo6NbrAsP-XtvBaXFg.png)](https://logrocket.com/signup/)<figcaption><a href="https://logrocket.com/signup/">https://logrocket.com/signup/</a></figcaption>

[LogRocket](https://logrocket.com/signup/) is a frontend logging tool that lets you replay problems as if they happened in your own browser. Instead of guessing why errors happen, or asking users for screenshots and log dumps, LogRocket lets you replay the session to quickly understand what went wrong. It works perfectly with any app, regardless of framework, and has plugins to log additional context from Redux, Vuex, and @ngrx/store.

In addition to logging Redux actions and state, LogRocket records console logs, JavaScript errors, stacktraces, network requests/responses with headers + bodies, browser metadata, and custom logs. It also instruments the DOM to record the HTML and CSS on the page, recreating pixel-perfect videos of even the most complex single page apps.

[Try it for free.](https://logrocket.com/signup/)

* * *