Book Overview & Buying
Table Of Contents
Feedback & Rating

Mastering Reactive JavaScript

By : Erich de Souza Oliveira

3.5 (4)

Buy this Book

Mastering Reactive JavaScript

3.5 (4)

By: Erich de Souza Oliveira

Buy this Book

Overview of this book

If you’re struggling to handle a large amount of data and don’t know how to improve your code readability, then reactive programming is the right solution for you. It lets you describe how your code behaves when changes happen and makes it easier to deal with real-time data. This book will teach you what reactive programming is, and how you can use it to write better applications. The book starts with the basics of reactive programming, what Reactive Extensions is, and how can you use it in JavaScript along with some reactive code using Bacon. Next, you’ll discover what an Observable and an Observer are and when to use them.You'll also find out how you can query data through operators, and how to use schedulers to react to changes. Moving on, you’ll explore the RxJs API, be introduced to the problem of data traffic (backpressure), and see how you can mitigate it. You’ll also learn about other important operators that can help improve your code readability, and you’ll see how to use transducers to compose operators. At the end of the book, you’ll get hands-on experience of using RxJs, and will create a real-time web chat using RxJs on the client and server, providing you with the complete package to master RxJs.

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

What Does Being Reactive Mean?

The reactive paradigm

Why do I need it?

Installation of tools

Your first code using reactive programming

Summary

Reacting for the First Time

The bacon.js observables

Reacting to changes

Reading how an operator works

Transforming events using bacon.js

Summary

A World Full of Changes - Reactive Extensions to the Rescue

RxJS observables

Subscribing to changes (Observer)

RxJS Subjects

RxJS Disposable

RxJS Schedulers

Summary

Transforming Data - Map, Filter, and Reduce

Adding operators to observables

The map() operator

The flatMap() operator

The filter() operator

The reduce() operator

Summary

The World Changes Too Fast - Operators to Deal with Backpressure

What is backpressure?

Common strategies to deal with backpressure

More ways to filter data

Summary

Too Many Sources - Combining Observables

When do I need to combine observables?

Running observables

Concatenating observables

Combining observables

Summary

Something is Wrong - Testing and Dealing with Errors

Dealing with errors

Acting when an error occurs

Summary

More about Operators

The road so far

The fundamentals of RxJS

Going beyond the basics

Other important operators

Summary

Composition

What is a transducer?

Available transducer implementations for JavaScript

The transducers-js API

Using transducers

Using transducers with RxJS

Testing transducers

A performance comparison for JavaScript code using transducers

Summary

A Real-Time Server

The web chat server

Creating the project

The architecture of the server

Implementing the server

Scaling the server

Summary

A Real-Time Client

Installing dependencies

The structure of our client

Building the application for the first time

Connecting to the server application

Using RxJS to manage user input

Connecting user interactions and server communication

Improving interaction with RxJS

Batching changes to the DOM

Testing the application

Summary

Customer Reviews

3.5 (4)

5 star

50%

4 star

3 star

2 star

50%

1 star

Batching changes to the DOM

When developing a frontend application, one of the greatest problems for performance is the access to DOM.

Changing or adding nodes in the DOM can have a serious impact on your application's performance.

Using RxJS, we can easily mitigate this problem using buffers to aggregate changes before applying it to the DOM. In our web chat application, every time a user sends a message or you send a message, we need to add a new node in the DOM. Given the nature of our application, we do not expect to receive several messages per second (or the user will not be able to read the messages), but if you were implementing a chart with real-time data, this behavior can quickly become a bottleneck for you.

Here, in this section, we are going to do a minor change to our application so all changes in the DOM are buffered before being applied. I will show this technique as it can be used in several...