Security and performance for today’s developer
Although some issues, such as cache invalidation, have been largely fixed, many challenges remain with respect to traditional CDNs. For example, requests to purge stale content on traditional CDNs often end up in an aggregate purge queue, and the process can take anywhere from a few seconds to several minutes. There may also be limits on the number of purges that can be requested per second. All of this makes it difficult for developers to quickly deliver dynamic content based on personalization data, such as location, device type, or account information.
Comments are closed, but trackbacks and pingbacks are open.