Why is Drupflare Faster?

Most Drupal hosting puts every visitor on a long trip to one server, which then asks a separate database for the page. Drupflare removes both trips.

• The site runs in the Cloudflare location nearest each visitor instead of one data center, so the network round trip that dominates a normal page load mostly disappears.
• Each site's SQLite sits in the same Durable Object as PHP. A query is a function call, not a connection to another machine.
• The interpreter loads once and serves request after request. A fresh isolate starts it in 5 ms.
• Published pages are stored and served straight from cache, and re-rendered in the background when content changes. This means PHP is rarely executed.
• When logged-in traffic starts to queue, the site adds replicas, or full copies of itself that answer in parallel from their own database. Sixteen replicas serve 4.74x the traffic of a single copy, and the median wait falls 24.8x at 64 concurrent visitors. Nobody resizes a server.
• A logged-in session is answered from a plan compiled after its first few requests: /admin/content in 5 ms, where nginx with PHP-FPM took 71 ms on the same machine.

The result is a Drupal site that behaves like a static one for visitors and stays fully dynamic for the people editing it.

This leads to a 6x faster Drupal site on someone on the same continent, and upwards of 25x+ faster when dealing with someone on the other side of the world.