Asset Versioning

ibexa Lösungen / inwebco ibexa / Page Builder Features / Asset Versioning

Changing various assets is an essential part of web development. Browsers store these assets in the local cache so that they only have to retrieve them the first time the web page is loaded, which speeds up the loading process.

This results in the problem that browsers do not promptly register a change in the assets and thus continue to display old assets that have already been changed.

With the help of asset versioning, assets are updated immediately after a deployment without losing the benefits of the browser cache.

ESI

ESI allows targeted updating of the cache within a web page without having to update the entire cache.

Reactive cache

We have made extensive adjustments to the caching system that allow us to have the cache within a webpage update only the data that has changed, rather than blanket updates of the entire webpage.

Varnish

Varnish enables through the caching that a call of the page by a user does not have to go through all the remaining areas of a page. This stores a current state of the URL and can thus be passed directly to the browser with significant performance gain. No further queries are necessary, whereby an enormously high availability and fast delivery of the website is achieved even with few servers.




inwebco eZ Platform / Page Builder Erweiterung
inwebco ibexa / Page Builder Extension
We have used the accumulated experience of our projects and extended ibexa and Page Builder with some powerful improvements. These range from the implementation of common technologies, to the optimization of configurations or technical developments.
inwebco ibexa / Page Builder