from v2.4.0 the manager started to use caching on the front-side using IndexedDB
but i found a way to also cache it on the back-side using flysystem
Quick Comparison
Front
Back
package size
14.35kb
84kb
cache clearing
with a button (browser level)
manually (server level)
cache invalidation
easy
hard
access speed
user dependent
(global) very fast
Cast Your Vote
Update
as it seems more users are in favor of front cacheing as-well as its also easier for me to reason with the invalidation,
as of v3.0.0 a new option for cache invalidation has been added which makes it far easier to work with instead of the backend solution.
from
v2.4.0the manager started to use caching on the front-side using IndexedDBbut i found a way to also cache it on the back-side using flysystem
Quick Comparison
Cast Your Vote
Update
as it seems more users are in favor of front cacheing as-well as its also easier for me to reason with the invalidation, as of
v3.0.0a new option for cache invalidation has been added which makes it far easier to work with instead of the backend solution.