Currently applications can invalidate cache by running booster tasks.
But execution will fail if booster app in stopped/not installed. And it needlessly binds app logic to booster app.
Instead application may send a custom event and booster app may be configured (siteConfig) to invalidate the cache by configured events.
Currently applications can invalidate cache by running booster tasks.
But execution will fail if booster app in stopped/not installed. And it needlessly binds app logic to booster app.
Instead application may send a custom event and booster app may be configured (siteConfig) to invalidate the cache by configured events.