RxJS

NOTE: The latest version of RxJS can be found here The Need to go Reactive | About the Reactive Extensions | Batteries Included | Why RxJS? | Dive In! | Resources | Getting Started | What about my libraries? | Compatibility | Contributing | License The Reactive Extensions for JavaScript (RxJS) 4.0... ...is a set of libraries to compose asynchronous and event-based programs using observable collections and Array#extras style composition in JavaScript The project is actively developed by Microsoft, in collaboration with a community of open source developers. The Need to go Reactive Applications, especially on the web have changed over the years from being a simple static page, to DHTML with animations, to the Ajax revolution. Each time, we're adding more complexity, more data, and asynchronous behavior to our applications. How do we manage it all? How do we scale it? By moving towards "Reactive Architectures" which are event-driven, resilient and responsive. With the Reactive Extensions, you have all the tools you need to help build these systems. About the Reactive Extensions The Reactive Extensions for JavaScript (RxJS) is a set of libraries for composing asynchronous and event-based programs using observable sequences and fluent query operators that many of you already know by Array#extras in JavaScript. Using RxJS, developers represent asynchronous data streams with Observables, query asynchronous data streams using our many operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, RxJS = Observables + Operators + Schedulers. Whether you are authoring a web-based application in JavaScript or a server-side application in Node.js, you have to deal with asynchronous and event-based programming. Although some patterns are emerging such as the Promise pattern, handling exceptions, cancellation, and synchronization is difficult and error-prone. Using RxJS, you can represent multiple asynchronous data streams (that come from diverse sources, e.g., stock quote, tweets, computer events, web service requests, etc.), and subscribe to the event stream using the Observer object. The Observable notifies the subscribed Observer instance whenever an event occurs. Because observable sequences are data streams, you can query them using standard query operators implemented by the Observable type. Thus you can filter, project, aggregate, compose and perform time-based operations on multiple events easily by using these operators. In addition, there are a number of other reactive stream specific operators that allow powerful queries to be written. Cancellation, exceptions, and synchronization are also handled gracefully by using the methods on the Observable object. But the best news of all is that you already know how to program like this. Take for example the following JavaScript code, where we get some stock data and then manipulate and iterate the results. /* Get stock data somehow */ const source = getAsyncStockData(); const subscription = source .filter(quote => quote.price > 30) .map(quote => quote.price) .forEach(price => console.log(`Prices higher than $30: ${price}`)); Now what if this data were to come as some sort of event, for example a stream, such as a WebSocket? Then we could pretty much write the same query to iterate our data, with very little change. /* Get stock data somehow */ const source = getAsyncStockData(); const subscription = source .filter(quote => quote.price > 30) .map(quote => quote.price) .subscribe( price => console.log(`Prices higher than $30: ${price}`), err => console.log(`Something went wrong: ${err.message}`) ); /* When we're done */ subscription.dispose(); The only difference is that we can handle the errors inline with our subscription. And when we're no longer interested in receiving the data as it comes streaming in, we call dispose on our subscription. Note the use of subscribe instead of forEach. We could also use forEach which is an alias for subscribe but we highly suggest you use subscribe. Batteries Included Sure, there are a lot of libraries to get started with RxJS. Confused on where to get started? Start out with the complete set of operators with rx.all.js, then you can reduce it to the number of operators that you really need, and perhaps stick with something as small as rx.lite.js. If you're an implementor of RxJS, then you can start out with rx.core.js. This set of libraries include: The complete library: rx.all.js Main Libraries: rx.js rx.aggregates.js rx.async.js rx.binding.js rx.coincidence.js rx.experimental.js rx.joinpatterns.js rx.testing.js rx.time.js rx.virtualtime.js Lite Libraries: rx.lite.js rx.lite.extras.js rx.lite.aggregates.js rx.lite.async.js rx.lite.coincidence.js rx.lite.experimental.js rx.lite.joinpatterns.js rx.lite.testing.js rx.lite.time.js rx.lite.virtualtime.js Core Libraries: rx.core.js rx.core.binding.js rx.core.testing.js Why RxJS? One question you may ask yourself is why RxJS? What about Promises? Promises are good for solving asynchronous operations such as querying a service with an XMLHttpRequest, where the expected behavior is one value and then completion. Reactive Extensions for JavaScript unify both the world of Promises, callbacks as well as evented data such as DOM Input, Web Workers, and Web Sockets. Unifying these concepts enables rich composition. To give you an idea about rich composition, we can create an autocompletion service which takes user input from a text input and then throttles queries to a service (to avoid flooding the service with calls for every key stroke). First, we'll reference the JavaScript files, including jQuery, although RxJS has no dependencies on jQuery... <script src="https://code.jquery.com/jquery.js"></script> <script src="rx.lite.js"></script> Next, we'll get the user input from an input, listening to the keyup event by using the Rx.Observable.fromEvent method. This will either use the ev