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.
Table of Contents (12 chapters)

Summary

We have gone through a lot in this chapter. Among the things covered have been installing and using the store. To that knowledge, we have added some sound best practices to organize your code. It's important to note that consistency is key. There are many ways to organize code, so as long as that chosen way remains consistent throughout the app, that is the most important factor. With that said, organizing your code by domain is what is prescribed for most things Angular. Whether that holds true for NgRx is up to you, dear reader. See best practices as a guide rather than a rule. Furthermore, we covered side effects and how to handle those with @ngrx/effects. @store-devtools was another thing we covered, which lets us use our browser to easily debug our store. In the next, and final, chapter, we will cover @ngrx/schematics and @ngrx/entity, so we really cover everything...