L2 Caching is an Edge Application module that creates an additional cache layer between the edge and your origin servers, reducing latency and infrastructure costs.
When accessing your applications on Azion, your end-user accesses the edge network, where your content is cached. By enabling L2 Caching in Edge Application, you can:
- Cache at a second layer at the edge.
- Keep your content cached for longer periods of time.
- Select the best region to keep cache closer to your users.
ImplementationSection titled Implementation
|Edge Caching module||Edge Caching|
|Creating a cache setting||How to configure cache policies for Edge Application|
Recommended TTLSection titled Recommended TTL
L2 Caching is specially designed for objects that can remain in cache for a long period of time. Thus, you can only activate it on cache policies with a TTL equal to or greater than 3 seconds, with the default TTL being 60 seconds.Learn more about expiration settings
RegionsSection titled Regions
When you enable L2 Caching as an extra caching layer, the edge servers of this second caching layer are hosted in the US (
na-united-states) by default.
Azion also offers the option of hosting the L2 servers in Brazil (
sa-brazil). To switch between regions in your edge applications, please contact the Sales team.
Real-Time PurgeSection titled Real-Time Purge
Whenever necessary, you can use Real-Time Purge to expire your L2 Caching content before the expected TTL time. Remember to purge first in L2 and only later in Edge Caching. This avoids edge feedback with outdated L2 content.Learn more about Real-Time Purge
LimitsSection titled Limits
Bypass cacheSection titled Bypass cache
The L2 Caching module currently doesn’t support bypass cache. You can configure a Bypass Cache rule for caching at the edge, but applications with active L2 cache settings will continue to keep caching in that layer for the specified TTL.Learn more about Bypass Cache