Cloudflare is the public delivery and traffic-management layer for CoreSpeed. It is not used only for authoritative DNS.
A typical request follows this path:
Visitor → Cloudflare edge → CoreSpeed Worker and cache → CoreSpeed origin → WordPress
Within this architecture, Cloudflare provides:
- Authoritative DNS or O2O traffic routing
- Reverse proxying
- Worker execution
- Edge caching
- Globally accessible Workers KV storage
- Origin routing
- TLS termination
- Request and response processing
- Prelaunch preview routing
CoreSpeed’s origin infrastructure is managed separately through standardized server automation. SiteCare applies tier-based configuration for PHP-FPM, Redis, MySQL, and other server resources.
Why the Cloudflare layer matters
CoreSpeed uses a custom Cloudflare Worker to control how requests are cached, routed, and forwarded to WordPress. Cloudflare Workers run in the request path and can modify both the request sent toward the origin and the response returned to the visitor.
For public, cacheable pages, CoreSpeed can respond from Cloudflare rather than requiring WordPress to execute PHP and query MySQL for every request.
The CoreSpeed caching system uses:
- Cloudflare’s Cache API for edge responses
- Workers KV as a globally accessible backing layer
- A WordPress plugin that notifies the Worker when content changes
- SiteCare-defined rules for cookies, query parameters, and dynamic routes
The internal cache implementation stores responses in Cloudflare’s cache and uses Workers KV to reduce origin requests when a regional cache does not already contain the page.
Why SiteCare needs control of this layer
SiteCare is responsible for the behavior of the complete delivery path, not only the origin server.
That requires us to manage or support:
- DNS records and proxy status
- Worker deployments
- Worker routes
- KV bindings
- Cache configuration
- Custom hostnames
- Origin routing
- TLS configuration
- Rules that may change requests or responses
Separating those responsibilities among unrelated vendors can make it difficult to determine whether a problem is occurring in DNS, Cloudflare, the Worker, the origin, or WordPress.
CoreSpeed is structured so SiteCare can diagnose and support the entire request path.
Comments
0 comments
Please sign in to leave a comment.