Birthday week: Cloudflare turns 10 Meta Image
Birthday week: Cloudflare turns 10 Embedded Image - 2EA2Ho

Cloudflare's tenth birthday week was held online rather than in person, and the announcements followed the usual day-by-day format. What follows is a condensed record of what shipped between Monday and Friday, plus the numbers behind it.

Workers: stateful storage and scheduled execution

Workers was introduced during Birthday Week 2017, and the 2020 additions push further into use cases the original serverless edge model did not cover.

Workers KV already provided high availability storage at the edge, but functions-as-a-service is fundamentally stateless. Some workloads need consistency — one view of the data for every requester — more than they need availability. Workers Durable Objects gives developers high consistency storage on the platform: when two people race to buy the same concert ticket, the system has to make sure only one of them succeeds, which a database in a single location handles naturally and a globally distributed Workers deployment does not.

The other gap was invocation. Workers were historically triggered by user action, such as a request to a URL. Sync jobs, batch jobs, or actions scheduled 24 hours after a user does something do not follow that pattern. Cron Triggers remove the dependence on someone doing something.

Analytics: no cookies, and the user's point of view

Conventional web analytics tracks individual users through client-side state such as cookies or localStorage, or through fingerprints. Two problems follow: a principled one, since site owners who object to being tracked should not impose tracking on their visitors; and a practical one, since users who dislike tracking increasingly block these tools, which makes their numbers less accurate over time.

The new Web Analytics product avoids client-side state entirely. No cookies or localStorage are used to track users, and Cloudflare does not fingerprint individuals by IP address, User Agent string or other data to present analytics — fingerprinting is considered more intrusive than cookies because users cannot opt out. Cloudflare's business is not built on tracking users or selling advertising, so the product collects metrics only.

On the performance side, Cloudflare integrated Google's Web Vitals into Browser Insights. Edge-side performance analytics were already available; the addition blends the server's view of performance with how users actually perceive it, and presents the combined data in a form meant to show what needs optimizing. Google uses a blended performance measure when ranking sites in search results, and the Chrome team's Web Vitals work underlies the metric.

Radar, and moving HTTPS negotiation into DNS

Cloudflare now sits in front of 14.5% of the world's top 10 million websites. Each second it handles roughly 18 million HTTP requests and 6 million DNS requests, blocks 72 billion cyberthreats per day, and sees 1 billion unique IP addresses connect to its network. That gives it one of the most representative views of worldwide Internet traffic.

Previously that data stayed internal, used to improve the service and protect customers. Cloudflare Radar exposes it externally, making the Internet's traffic patterns publicly visible — comparable to a city's traffic reporting service, but for patterns that run on a global scale.

Radar-style observation is also how one performance change began. In late June, the team noticed spikes in DNS requests for the 65479 Resource Record; they traced back to Apple's iOS14 beta, which was testing a new SVCB/HTTPS record type. The underlying problem: when a user types a URL without a protocol, the browser begins with HTTP and the initial negotiation happens in plaintext before the transition to an HTTPS or HTTP/3 resource. That costs latency and weakens security.

Because a DNS request always precedes HTTP negotiation, the DNS query can carry the answer. Cloudflare's DNS servers now automatically generate HTTPS records on the fly to advertise whether a zone supports HTTP/3 and/or HTTP/2, based on which features are enabled for that zone. The result is improved performance and improved security together.

API day: gRPC and API Shield

Most REST APIs use HTTPS and JSON, which are designed for humans talking to computers. That keeps payloads readable but makes them inefficient, and the inefficiency multiplies as API traffic grows. gRPC is an efficient protocol for computers talking to each other — but because it uses newer technology such as HTTP/2 underneath, existing security and performance tooling did not support gRPC traffic out of the box, forcing teams to choose between a modern API protocol and security, performance and reliability.

Cloudflare's beta support for gRPC removes that trade-off. Once gRPC APIs sit behind Cloudflare, Argo Smart Routing reduces time to first byte, a Load Balancer adds reliability, and Bot Management and the WAF add security.

Protecting APIs is not the same as protecting websites, though. The WAF looks for attack patterns aimed at breaking how a browser interacts with a site or a bot interacts with a site; machine-to-machine traffic presents different vectors. API Shield is built for those vectors with strong client certificate-based authentication and strict schema-based validation. Authentication uses mutual TLS, which is not exposed to password or token reuse and sharing. With only legitimate clients — holders of the right SSL certificates — connecting, the next check is request validity: query parameters after the URL and the contents of the POST body are matched against a contract or schema describing what is expected. Failed validation blocks the call so the origin never receives an invalid request or malicious payload. gRPC and API Shield support each other out of the box.

Automatic Platform Optimization, starting with WordPress

Caching static assets has always been part of the platform and remains a strong lever when an origin is slow or a user is far away; it also reduces origin load. Dynamic content is the harder case, and because Cloudflare cannot know whether HTML will change per user, it does not cache HTML by default.

In practice most HTML is not truly dynamic. It must change quickly when the site is updated, but for a large share of the web the content is stable for months or years, and most visits come from anonymous users, with logged-in views forming an exception. Automatic Platform Optimization adds the intelligence to decide when HTML should be cached and when it shouldn't, moving more content closer to users with no configuration required. At the 90th percentile for desktop users, Cloudflare reports a 72% reduction in Time to First Byte (TTFB), 23% reduction to First Contentful Paint and 13% reduction in Speed Index. Support starts with WordPress, which runs 38% of all websites, with other platforms to follow.

Ten years, on Cloudflare TV

The birthday was also an occasion to look back at a decade of the Internet and ahead to the next one, through 24 hours of live discussions streamed over the week on Cloudflare TV. Participants included Apple co-founder Steve Wozniak, Zoom CEO Eric Yuan, OpenTable CEO Debby Soo, Stripe co-founder and President John Collison, former Google CEO and Executive Chairman and Schmidt Futures co-founder Eric Schmidt, former McAfee CEO Chris Young, former Seal Team 6 Commander Dave Cooper, and Project Include CEO Ellen Pao, among many others.