Book Image

Architecting Angular Applications with Redux, RxJS, and NgRx

By : Christoffer Noring
Book Image

Architecting Angular Applications with Redux, RxJS, and NgRx

By: Christoffer Noring

Overview of this book

Managing the state of large-scale web applications is a highly challenging task with the need to align different components, backends, and web workers harmoniously. When it comes to Angular, you can use NgRx, which combines the simplicity of Redux with the reactive programming power of RxJS to build your application architecture, making your code elegant and easy to reason about, debug, and test. In this book, we start by looking at the different ways of architecting Angular applications and some of the patterns that are involved in it. This will be followed by a discussion on one-way data flow, the Flux pattern, and the origin of Redux. The book introduces you to declarative programming or, more precisely, functional programming and talks about its advantages. We then move on to the reactive programming paradigm. Reactive programming is a concept heavily used in Angular and is at the core of NgRx. Later, we look at RxJS, as a library and master it. We thoroughly describe how Redux works and how to implement it from scratch. The two last chapters of the book cover everything NgRx has to offer in terms of core functionality and supporting libraries, including how to build a micro implementation of NgRx. This book will empower you to not only use Redux and NgRx to the fullest, but also feel confident in building your own version, should you need it.
Table of Contents (12 chapters)


We have now covered core concepts such as Observable, Observer, Producer, and operators. We have also looked into how we can manually create an Observable, but realized that there are different creation operators that will help you create Observables from other constructs, and sometimes the Angular framework itself will create the Observable for you. We have failed to mention one important thing though, cleanup. There will be situations where an Observable will allocate resources or simply go on forever, as with the interval() operator. There is one clear remedy to that—define and run a cleanup function when we are done with the Observable. Defining such a function forces us to return to the create operator and amend some code in its behavior function, like so:

let stream$ = Rx.Observable.create(observer => {
let counter = 0;
let id = setInterval(() => observer...