
User requests hit the
CrowdDirector™ globally distributed service platform at the closest Redirector entry point. Redirector gateways are distributed on all continents.

Each CNAME or NS delegation bound to the
CrowdDirector™ Rules engine is evaluated based on the routing logic that you configure through the Rules Management System (time, geo, network, URL specifics‚Ķ). Each request is accounted for and graphed in the Stats Engine, and answered with a resulting
host name.

The delegated NS response or HTTP redirect being issued then targets your relevant
CrowdCache™ named pool within which it is then automatically load balanced according to your own tuning. If content is already in local cache, the resulting
CrowdCache™ node will serve it.

If content isn't already in the local cache of the landing
CrowdCache™, your custom Origin Mappings will allow you to either proxy or redirect while dynamically feeding the local cache. These Origin Mappings are configured online or through an API on the CrowdCache Management interface.