CDN (Content Delivery Network)

A content delivery network (CDN) is a geographically distributed system of servers — called edge nodes or points of presence (PoPs) — that caches and delivers web content from locations closest to the end user. Instead of every request traveling to a single origin server, a CDN stores copies of static assets (images, scripts, fonts, stylesheets) at dozens or hundreds of edge locations worldwide. When a reader requests content, the CDN routes that request to the nearest available node. This reduces network latency, speeds up load times, and distributes the traffic load so no single server becomes a bottleneck.

Page load speed directly affects user engagement, bounce rates, and search engine rankings. Flipbooks and digital documents contain high-resolution page images, JavaScript rendering engines, and font files that add up to significant download sizes. Serving all of this from a single origin server means that a reader on a different continent may wait several seconds for the first page to appear. A CDN eliminates that geographic penalty by placing cached content within milliseconds of every reader. CDNs also absorb traffic spikes — if a publication goes viral or gets sent to a large mailing list, the edge network handles the surge without overloading the origin.

FlipLink serves all published flipbooks and documents through a CDN automatically. When a reader opens your publication, assets like page images, scripts, and fonts are delivered from the edge server nearest to their location. You do not need to configure anything; CDN delivery is built into every publication. This infrastructure also absorbs traffic spikes, so a flipbook that suddenly goes viral will not slow down or become unavailable. Combined with FlipLink's optimized rendering pipeline, CDN delivery keeps the [page experience](/features/page-experience-and-layout) fast worldwide. If you use a [custom domain](/features/custom-domains) for your publications, CDN delivery still applies — readers on your branded domain get the same edge-served performance.

CDNs operate using a pull-based caching model. The first request for a resource goes to the origin server, and the CDN caches the response at the edge node that handled it. Subsequent requests from the same region are served directly from cache, bypassing the origin entirely. Key technical concepts include: - **Cache TTL (Time to Live)**: How long an edge node holds a cached copy before checking the origin for updates. FlipLink sets appropriate TTLs so published content stays fresh while maximizing cache hits. - **Cache invalidation**: When you update a publication, the CDN purges stale copies so readers see the latest version. FlipLink handles invalidation automatically when you republish. - **TLS termination**: CDN edge nodes handle HTTPS encryption, so the secure connection terminates close to the reader rather than at a distant origin, reducing handshake latency. - **Anycast routing**: DNS queries resolve to the geographically nearest CDN node, so traffic is automatically directed to the optimal location without manual configuration.

| Aspect | Origin Server Only | With CDN | |---|---|---| | Latency | High for distant readers | Low everywhere | | Traffic capacity | Limited by single server | Distributed across edge network | | Availability | Single point of failure | Redundant across many nodes | | Cost scaling | Server upgrades needed | Edge network absorbs load | | Global performance | Inconsistent | Consistent worldwide | Without a CDN, a reader in Sydney accessing a server in Frankfurt experiences 300+ milliseconds of network round-trip time before content even begins loading. With a CDN, that same reader hits a local edge node and sees the first page in a fraction of the time.

A CDN is invisible infrastructure that makes a measurable difference. Every published FlipLink flipbook benefits from global CDN delivery automatically — no configuration, no extra cost, and no performance compromises for readers anywhere in the world.