You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now a lot of components have to pass data causing long pass through streams of certain information.
Introducing a caching layer would allow these components to do a request by themselves.
If the data has already been fetched, it would not send a request, but rather return the cached result.
The cache layer should have the following characteristics:
Cache is session specific.
Reloading the page will not serve the same cache, but rather build a new one. This is important since the data present is rather subjective to change.
Cache should be updated automatically when updating/deleting data
Eg: when a project is deleted using DELETE /projects/{id} it should also be deleted from GET /projects or GET /projects/{id}
Cache should work completely transparent to the components
The text was updated successfully, but these errors were encountered:
Right now a lot of components have to pass data causing long pass through streams of certain information.
Introducing a caching layer would allow these components to do a request by themselves.
If the data has already been fetched, it would not send a request, but rather return the cached result.
The cache layer should have the following characteristics:
Cache is session specific.
Reloading the page will not serve the same cache, but rather build a new one. This is important since the data present is rather subjective to change.
Cache should be updated automatically when updating/deleting data
Eg: when a project is deleted using
DELETE /projects/{id}
it should also be deleted fromGET /projects
orGET /projects/{id}
Cache should work completely transparent to the components
The text was updated successfully, but these errors were encountered: