No matter how Big
Purge System

Caching is the key technology of the CDN service to seamlessly deliver various content to online users. In general, CDN services receive files from the origin server by user request through caching, cache them on the edge cache server, and deliver them to the end user.

It delivers the cached content from the edge cache server, not the origin server, to the online user who requested the content. The cache server at the edge checks the origin server for content changes at regular intervals to provide valid content.

If there are any changes to the original content, it will provide the content viewer with the updated cached content. Using purge function, which is the required key feature of CDN service allows, a service provider to deliver content at the scheduled timeslot.

The purge function is as important as caching function to handle tons of static content, such as online games that frequently patch large quantities, shopping malls that newly change images and information, and online education that communicates with online users and generates content in real time.

The purge method can both invalidate (soft purge) or delete (hard purge) cached content on the edge cache server to serve with content that is different from the original one.


The Solbox Purge method consists of a high-performance, safe and easy-to-use system to run a big scale of purge requests and real-time purges for a large service provider.

In addition, through continuous feature enhancement, Solbox purge system can handle purge tasks of an average of 2 million purge requests per day at an average speed of 10ms.
For the service convenience, it supports the RESTful API as well as the customer-specific web UI and provides a pattern purging that allows a purge request to a file with the same path or name.

Solbox CDN service allows a service provider to use our purge system to quickly update the content for various purposes and operate the service efficiently and reliably.
However, just keep in mind that the purge operation may place an excessive load on the edge cache server and the origin server.