A CDN, or content delivery network, caches your assets in geographically distributed locations to make downloads and page loads faster for your users.

You should use a CDN in front of Spaces if:

Your use case is mostly serving GET requests from the Internet, especially for frequent requests to small files.
For example, web-facing applications and media servers are especially likely to see significant performance improvements with the addition of a CDN.
By integrating a CDN with Spaces, you can distribute content to your users with low latency and a higher data transfer rate than you could get by serving your content directly from Spaces.

A CDN will fetch requested files from Spaces and cache them closer to your end users. By serving future requests for the same files from the CDN’s cache, you reduce the number of GET requests sent to Spaces and therefore reduce the user’s overall latency when interacting with your application.