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)

Leveraging types and feature modules

The following files is pointing to the demo project Chapter9/FeatureModules.

OK, one thing we can definitely improve is how we tell the StoreModule about what state and reducers exist in our app. Let's do a quick recap and look at its current state:

// from app.module.ts

StoreModule.forRoot({ count: counterReducer, jediList: JediListReducer })

So, we are essentially feeding the forRoot() method an object. What's wrong with that? Well, imagine you have ten different feature modules and every feature module may have three to four states, then the object you pass to forRoot() will grow in size and the number of imports that you need to do in your app.module.ts will grow. It will look something like this:

featureModuleState1: featureModuleState1Reducer,
featureModuleState2 : featureModuleState2Reducer