Support for SSR caching #1820
Replies: 1 comment 1 reply
-
Another idea that came up while discussing the problem with @shyim during SCUC22 is to use and maybe adapt the current varnish implementation for the storefront. You would use the same cache-tags in the PWA that are used in Shopware itself, but that shouldn't be a big problem as they are defined and the list/structure can be provided. https://developer.shopware.com/docs/guides/hosting/infrastructure/reverse-http-cache EDIT: I think there would also another possibilty to do it for the PWA: on every SSR the following could happen
Varnish config could then look like it's done e.g. in Drupal. The BAN-Request would then be made with a header too containing the cache tags that should be invalidated. |
Beta Was this translation helpful? Give feedback.
-
This is a open question to everyone and especially the team: what's your take on potentially implementing a SSR-cache?
To be clear: I don't think this should be implemented by default, but rather an option to use it (maybe with a guide in the docs).
I saw that there is a nuxt-module from vuestorefront, which provides ssr-caching functionality as a nuxt-module: https://docs.vuestorefront.io/v2/performance/ssr-cache.html
Do you think this could be used with shopware-pwa, especially for heavy routes like CMS, categories and product-detail pages? What would be the challenges in your point of view?
I'm not quite sure if changes have to be made how the sw-context is handled, because if you'd cache the routes mentioned right now, every client would get the same context, am I right? Beyond that I don't see any obvious obstacles, but I could be wrong of course...
Beta Was this translation helpful? Give feedback.
All reactions