Book Image

Architecting Angular Applications with Redux, RxJS, and NgRx

Book Image

Architecting Angular Applications with Redux, RxJS, and NgRx

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.

Related Content you might be interested in

Current Title:

Small book image
Architecting Angular Applications with Redux, RxJS, and NgRx
Mar, 2018 | 364 pages
Small book image
Reactive Patterns with RxJS for Angular
Lamis Chebbi
Apr, 2022 | 224 pages
Table of Contents (12 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Get in touch
Free Chapter
1
Quick Look Back at Data Services for Simple Apps
Quick Look Back at Data Services for Simple Apps
Model-View-Controller – the pattern we all know
An MVC flow in Angular
Using ES2015 modules
Dependency Injection
Fetching and persisting data with HTTP – introducing services with Observables
Summary
2
1.21 Gigawatt – Flux Pattern Explained
1.21 Gigawatt – Flux Pattern Explained
Core concepts overview
A uniform data flow
Demoing a uniform data flow
Adding more actions to our flow
Adding AJAX calls
An even bigger solution
Summary
3
Asynchronous Programming
Asynchronous Programming
The callback pattern
Problems with structuring async code – callback hell
Promises
Asynchronous libraries
Async/await
Summary
4
Functional Reactive Programming
Functional Reactive Programming
Functional programming versus imperative programming
Recursion
Asynchronous data streams
Comparing lists to async streams – preparing for RxJS
Summary
5
RxJS Basics
RxJS Basics
Observer pattern
RxJS core concepts
Creating Observables
Cleanup
Creating a core implementation of RxJS
Summary
6
Manipulating Streams and Their Values
Manipulating Streams and Their Values
Starting out
Stream in a stream
AJAX
A deeper look
Thinking in streams
Summary
7
RxJS Advanced
RxJS Advanced
Hot, cold, and warm Observables
Subjects
Error handling
Marble testing
Pipeable operators
Summary
8
Redux
Redux
Principles
Core concepts
Data flow
Dealing with asynchronous calls
Best practices
Summary
9
NgRx – Reduxing that Angular App
NgRx – Reduxing that Angular App
NgRx overview
@ngrx/store – state management
Best practices
Leveraging types and feature modules
Component architecture
@ngrx/store-devtools – debugging
@ngrx/effects – working with side effects
Summary
10
NgRx – In Depth
NgRx – In Depth
@ngrx/entity
@ngrx/router-store
Understanding NgRx – building our own micro implementation
@ngrx/schematics
Summary
11
Other Books You May Enjoy
Other Books You May Enjoy
Leave a review - let other readers know what you think

Asynchronous data streams

An asynchronous data stream is a stream of data where values are emitted, one after another, with a delay between them. The word asynchronous means that the data emitted can appear anywhere in time, after one second or even after two minutes, for example. A way to model asynchronous streams is to place the emitted values on a time axis, like so:

There are a lot of things that can be considered asynchronous. One such thing is fetching data through AJAX. When the data arrives depends on a number of factors, such as:

  • The speed of your connection
  • The responsiveness of the backend API
  • The size of the data, and many more factors.

The point is the data isn't arriving right at this very second.

Other things that can be considered asynchronous are user initiated events, such as scrolling or mouse clicks. These are events that can happen at any point in...

Previous Section
End of Section 4
Next Section