When the application has reached a large size a situation may arise in which having a given application state in several places we do not actually have a single source of truth a place where we will always receive the same result for a given query and not two completely different ones. When to choose application health management solutions? Let's imagine a situation in which an online store application in a browser renders two different prices for the same product even though they should be identical. Or a situation where the user has been logged out and the user's information is still displayed on the website.
Contrary to appearances when we do not rely on one source of truth there are many such situations and when this happens it is worth considering maybe it is time to use libraries to manage the state of the application? Such a decision should be made as early as possible when creating a web application because at a later stage it is often Email Marketing List impossible or involves reworking a large part of the code and adapting the old part of the application which is unfortunately very expensive. What is NgRx? So what is NgRx and how can it help us.
NgRx is a collection of libraries that are used to build reactive applications using Angular. Thanks to it we can manage the condition using among others isolated side effects. We have one source of truth so we will never have to wonder whether for example as in the example above the price of a given product is correct. When to use NgRx? NgRx for monitoring the state of the application is ideal for cases where a lot is happening in the UI layer.
發表於 2023-12-4 11:32:57
收藏