Filestack is very pleased to be able to offer CDN service to its customers!
Utilizing a content delivery network provides a better user experience for end users because the content is served to the user from the PoP (Point of Presence) closest to the user. A PoP, often reffered to as an "Edge Network", is a cluster of "Edge servers" whose purpose is to host content. When an asset is first requested, the user will hit the closest PoP location of the CDN, and if the asset does not exist at that location, it will be fetched from the origin (Filestack). Any subsequent request by that user or other users in that area for that asset will be delivered much faster because the file is replicated to a location that is closer in proximity to the user. Simple as that.
Filestack's network is rapidly expanding and its current PoP locations exist at high density internet exchange points and its Edge Servers use SSDs exclusively.
Benefits of using the Filestack CDN
Getting set up to use the Filestack CDN is incredibly easy. You actually don't have to do anything. All Filestack accounts are preconfigured to use the Filestack CDN. Now when you are returned a Filestack link, it will be from the Filestack CDN like this file here: https://cdn.filestackcontent.com/WZlsT9DkQTSbBbfn6WIP. The non-CDN link is still available at https://www.filestackapi.com/api/file/WZlsT9DkQTSbBbfn6WIP should you need it.
In order to get the best performance from Filestack, the Filestack CDN (cdn.filestackcontent.com) should be used. However, if you would prefer to use another CDN, Filestack can be configured to do this as well. Amazon operates the CloudFront CDN, a globally distributed content delivery network. Configuring CloudFront to work with the Filestack Web Framework is fairly simple, you just need to set the domain origin to https://www.filestackapi.com and then use the cloudfront links on your site. We present CloudFront as one alternative example — there are many other CDNs, and the steps required for integration will likely be similar.