Authorise first
Check access before sending protected bytes. A cached copy never grants additional permissions.
ARCHITECTURE
Storage and delivery, working together.
A delivery layer serves authorised requests. A placement layer uses demand signals to decide where content belongs. Each has its own responsibilities and safety boundaries.
CONTENT REQUESTSLOYRA
Access checkInvalid access → 403
DELIVERY CACHE
RAMFrequent reads
NVMe / SSDReusable content
HDDLong-tail content
CEPH STORAGESSD ↔ HDD
Two connected layers. One view of demand.
Ceph alone cannot see requests served from a local cache. The design tracks customer demand separately from physical origin reads so placement decisions can use both signals.
Read documentationClear responsibilities at every step
Keep local copies disposable
Delivery caches can be rebuilt from origin. They do not replace Ceph durability or backups.
Measure two kinds of demand
Record logical customer requests separately from origin reads, retries and background prefetch.
Move with verification
The target migration protocol copies, verifies and switches the catalog before removing the old copy.
Keep work off the request path
Telemetry batches, scans and migrations belong in bounded background jobs.
Roll out in stages
Start with observation and measurements. Enable automated placement only after adapter and failure testing.