Cache

Ibexa DXP uses HTTP reverse proxies (Varnish or Symfony's built-in HTTP cache) to serve fully cached responses at the edge. Content is tagged with repository IDs so that when an editor publishes a change, only the affected cache entries are purged — not the entire cache.

ESI (Edge Side Includes) allows personalised or dynamic fragments to be embedded inside otherwise fully cached pages. The result is near-static performance for anonymous traffic with targeted invalidation on editorial changes.

También te puede interesar

DXP
Digital Experience Platform. An integrated suite of tools for creating, managing, and delivering personalised digital experiences across all channels and touchpoints.
CDN
A Content Delivery Network caches assets and responses on globally distributed edge nodes, reducing latency for end users regardless of their geographic location.