Gain insights into reactive programming with RxJS. Learn about observables, operators, and concurrent programming to create real-world applications like a real-time earthquake visualizer and spaceship game.

_ Reactive Programming with RxJS by The Pragmatic Programmer_ .png

data.tar.gz

test rx

rx live

rx live-copy

rx live-earth

cycle

test rx-copy

cycle-rx

rx-cycle

test rx-copy-copy

cycle-rx-copy

cycle-rx-copymaham

qunit-job

In this course, you will learn about reactive programming techniques and use them to create real-world applications. Throughout this course, you will learn important concepts of RxJS programming such as observables, operators, concurrent programming, and how to build a complete web application.

Additionally, you will have the opportunity to build out applications for different real-world scenarios so that you can put what you learn into practice. You will use RxJS operators in scenarios such as the real-time earthquake visualizer and the reactive spaceship game.

By the end, you will have a new skill that you can utilize to build reactive programs as well as a few new projects to add to your portfolio.

Reactive Programming with RxJS

A combination of Observers and Observables

Which of the following acts like an `AsyncSubject`?

Which of the following acts like an <code>AsyncSubject</code>?

When a sequence is executed with an Observable

When does an `AsyncSubject` emit the last value?

When does an <code>AsyncSubject</code> emit the last value?

So that the `BehaviorSubject` can use it for other variables


So that subscribers can access that value

So that all the Observers always receive a value when they subscribe to a `BehaviorSubject`

Why does a `BehaviorSubject` require a starting value?

Why does a <code>BehaviorSubject</code> require a starting value?

Because we provide a default value in its constructor

Because we do not pass any value to its constructor

Because we always return a value in every function

Why does the `BehaviorSubject` guarantee that there will always be at least one value emitted?

Why does the <code>BehaviorSubject</code> guarantee that there will always be at least one value emitted?

Getting Started

Introduction to Reactive Programming with RxJS

Understanding the Reactiveness

Understanding the Observables

Understanding Sequencing and its Operators

Make a Real-time Earthquake Visualizer

Building Concurrent Programs Through Pipelines

RxJS Subject Class

Building a Reactive Spaceship to Keep the Application Pure

Building a Complete Web Application Using RxJS

Getting Real Time Updates from Twitter using Node.js

Schedulers

React Web Applications With Cycle.js and using Model View Intent

Closing Remarks

Quiz Yourself on RxJS Subject Class