Skip to main content

Safety beyond types

When a user causes mutations like creating, updating, or deleting resources, it's important to have those changed be reflected in the application. A simple publish cache that has no underlying knowledge of the data structures would require a refetch of any endpoints that are changed. This would reduce performance and put extra burden on the backend.

However, like many other cases, a normalized cache - one with underlying knowledge of the relationships between resources - is capable of keeping all data consistent and fresh without any refetches.


Reactive Data Client uses your schema definitions to understand how to normalize response data into an entity table and result table. Of course, this means that there is only ever one copy of a given entity. Aside from providing consistency when using different response endpoints, this means that by providing an accurate schema definition, Reactive Data Client can automatically keep all data uses consistent and fresh. The default update endpoints Resource.update and Resource.partialUpdate both do this automatically. Read more about defining other update endpoints


Reactive Data Client automatically deletes entity entries schema.Invalidate is used. Resource.delete provides such an endpoint.


Created entities are immediately available. They can also be added to existing Collections with .push, .unshift, or .assign.