Salesforce engineer details multi-tenant SaaS edge architecture built on Cloudflare Workers

Splitting the Edge Worker at SaaS Scale

An InfoQ article published September 23, 2026, walks through how Salesforce restructured a multi-tenant SaaS edge platform that runs on Cloudflare Workers, replacing a single monolithic worker that had accumulated image optimization, failover pages, routing, header and cookie rewriting, and per-tenant configuration lookups. The piece, written by Chintan Tank, a Principal Member of Technical Staff at Salesforce, and reviewed by AWS Data Hero Renato Losio, describes how the platform fronts the web traffic of hundreds of thousands of tenant accounts across more than one content delivery network and argues that at that scale the single-worker model becomes a deployment bottleneck. The recommended shape is a gateway worker paired with feature workers connected over service bindings, a split the author says decouples teams and blast radius without introducing an extra network hop.

Image Optimization as the Worked Example

The article uses image optimization to illustrate the build-or-buy decision that every edge feature faces. A CDN's zone-level image toggle is described as too coarse for multi-tenant SaaS, so format negotiation covering AVIF, WebP, and legacy formats, device-aware sizing, and per-tenant opt-out logic are implemented inside workers. The author frames this pattern as the template for treating each edge capability as an independently deployable unit rather than another responsibility stacked onto a shared entry point.

Akamai and Cloudflare Are Not Interchangeable

A section of the article warns that Akamai and Cloudflare differ enough in execution and deployment models that porting a feature between them is closer to re-architecting than to migrating. Maintaining parity across both CDNs is therefore treated as an ongoing constraint rather than a one-time effort. The implication drawn from the worked example is that teams must plan for cross-CDN compatibility when designing edge workers, not after the fact.

Per-Tenant Versioning and Testing Discipline

Because the platform serves hundreds of thousands of tenant accounts, the article argues that per-account versioning and staggered rollout stop being optional: the single-version model that works for one account becomes an all-or-nothing bet once that account becomes a tenant base. To keep independent feature teams from breaking one another, the author prescribes application-grade testing discipline, including unit suites per feature worker, integration tests at the gateway, and production synthetic monitoring, as the minimum bar for safe deployment at this scale.