📞 Caching Infrastructure

Architecture Overview

Aevum Encyclopedia employs a five-layer caching strategy that progressively serves content from the fastest available source, minimizing database load and ensuring global consistency.

Layer 1 — Edge CDN

Our edge CDN layer serves 78% of all requests directly from 142 global points of presence. Static assets, rendered article HTML, and API responses are cached at the edge with intelligent TTL management.

Cache-Control Headers

Purge Configuration

# aevum-cdn-purge.yaml
purge_rules:
  article_update:
    pattern: "/api/v2/articles/{id}"
    methods: ["GET", "PURGE"]
    propagation: "immediate"
    soft_purge: true

  category_bulk:
    pattern: "/api/v2/categories/{slug}/**"
    methods: ["GET"]
    propagation: "soft"
    stale_ttl: 300

  global_emergency:
    pattern: "*"
    methods: ["*"]
    requires_approval: true
    cooldown: 3600

Layer 2 — Redis Cluster

Aevum's Redis cluster operates across 6 geographic regions with active-active replication, storing serialized article payloads, user sessions, and computed knowledge graph edges.

Key Naming Convention

# Article cache keys
aevum:article:{locale}:{id}:full
aevum:article:{locale}:{id}:excerpt
aevum:article:{locale}:{id}:metadata

# Knowledge graph
aevum:graph:{topic}:edges
aevum:graph:{topic}:related

# Rate limiting
aevum:ratelimit:{user_id}:{endpoint}
aevum:ratelimit:global:{endpoint}

# Session data
aevum:session:{token}:data
aevum:session:{token}:preferences

Redis Cluster Topology

Cache Invalidation

When an article is edited by a contributor, our invalidation pipeline ensures all cache layers are updated in a coordinated fashion, preventing stale content from being served.

Invalidation Code Example

class CacheInvalidator:
    async def invalidate_article(self, article_id: str, locale: str):
        """Orchestrate multi-layer cache invalidation."""

Cache API

Aevum exposes a RESTful API for programmatic cache management. Use the X-Api-Key header for authentication.

Purge a Single Article

POST /api/v2/cache/purge/article/{id} HTTP/1.1
Host: cache.aevum-enc.com
X-Api-Key: sk_live_...
Content-Type: application/json

{
  "locale": "en",
  "reason": "editorial_update",
  "force_hard_purge": false
}

Monitoring & Alerting

Aevum's caching infrastructure is monitored via a real-time observability stack. Key metrics are tracked through Datadog, with custom dashboards for each cache layer.