Acceleration Flow

Assume the origin domain is origin.example.com and the acceleration domain is www.example.com. The acceleration flow through the CDN operates as follows:

1. The end-user requests a resource under www.example.com, such as www.example.com/index.html. The client first queries the local DNS server for the IP address of www.example.com.

2. The local DNS checks its cache for an existing record of www.example.com.

   • If cached, the IP is returned directly to the client.
   • If not cached, the local DNS queries the authoritative DNS server for the parsing record of www.example.com.

3. The authoritative DNS server responds with a CNAME record, for example:

   www.example.com → edge.conversant.swiftserve.com

4. The local DNS queries the Conversant Global Routing Management System for the IP address of edge.conversant.swiftserve.com. The system utilises client IP geolocation to identify the user’s region and ISP, evaluates real-time path quality metrics such as latency, packet loss, and jitter, and analyses the current load of candidate edge nodes. Based on these parameters, the system returns the optimal edge node IP address.

5. The local DNS returns the optimal edge node IP to the client.

6. The client sends the access request to the assigned edge node.

7. If the edge node already has the requested resource cached, the content will be responded to the client immediately.

8. If the resource is not cached or the cache has expired, the edge node retrieves the content from the origin server (origin.example.com), caches it according to the configured policy, and then delivers it to the client. Subsequent requests for the same resource will be served directly from the cache.