Optimizing Frontend Assets with CDN & OSS: Strategies for Global Acceleration

In the frontend engineering field, using CDN to accelerate web resources is common; beyond fast distribution, CDN also provides high throughput and security. This article shares practical experiences of combining CDN with Alibaba Cloud OSS to build flexible solutions for various scenarios.

1. Cache Time and Hit Rate

Under a CDN cache architecture, only when a request hits the CDN cache can access be accelerated. Cache hit rate depends on access frequency and cache duration. Versioned resources can have indefinite cache time, greatly improving hit rate, while low‑frequency resources may still trigger origin fetches due to limited cache space and eviction policies. For non‑versioned, overwrite‑type resources such as HTML or static config, long cache times are not recommended; if set too long, CDN cache invalidation can be costly and is limited for large‑scale operations.

2. Global Resource Acceleration

OSS has regional data centers with robust network access; combined with CDN, high‑hit pages experience negligible origin latency, and even low‑hit resources benefit from fast OSS access. However, for overseas users, if CDN nodes still pull from domestic OSS, cross‑border network congestion can cause timeouts. Using local CDN nodes to origin from local OSS data centers mitigates this, though it may require custom CDN support or DNS‑based regional resolution to direct requests to the nearest OSS bucket.

3. OSS Multi‑Region File Synchronization

OSS does not automatically sync across regions, so consistency must be ensured logically. Resources are categorized by business type (domestic, overseas) and further by geographic zones. The simplest approach is to publish to all regions simultaneously, but this wastes bandwidth and ties release success to every region. Instead, resources are tagged by access region: domestic resources sync only to domestic OSS, overseas‑specific resources sync to their respective regions, and globally accessed resources sync to all.

When most resources are versioned, OSS’s mirror‑origin feature simplifies publishing. A central OSS bucket serves as the source for other regions; if a region lacks a file, it fetches from the central bucket and caches it locally, reducing sync complexity and storage redundancy while ensuring fast access.