Fast globally distributed serverless database

If by “fast, globally distributed” you mean users around the world should get low-latency database access—not merely a serverless database that scales automatically—my default pick is CockroachDB Serverless.

My ranking

*Global writes involve unavoidable network latency when strong consistency is required.

🥇 Best overall: CockroachDB Serverless

If your app is genuinely global—users in the US, Europe, and Asia, for example—CockroachDB is the most compelling choice. It is designed as a distributed SQL database rather than a conventional database with replicas bolted on. You can distribute data across regions and control locality at the database/table/row level.www.cockroachlabs.com

That matters because replicating reads globally is easy; making globally distributed writes consistent is the hard part. CockroachDB is specifically designed around that problem.

The tradeoff is complexity/cost: you probably don't need CockroachDB if 95% of your users are in one region.

🥈 Best if you're building on Cloudflare: D1

If your app runs on Cloudflare Workers, I'd seriously consider Cloudflare D1.

D1 now supports automatic read replicas across Cloudflare's global regions. Reads can therefore execute near users, while writes go to the primary. Cloudflare's Sessions API provides sequential consistency across those replicas.developers.cloudflare.com

Cloudflare itself recommends D1 particularly for lightweight, read-heavy applications with global users.developers.cloudflare.com

The important caveat: D1 isn't a globally writable database. Writes still go to the primary database.developers.cloudflare.com

🥉 Best lightweight option: Turso

Turso is particularly interesting if your application fits SQLite. Its architecture is built around globally replicated SQLite-compatible databases and is especially attractive for edge applications, local-first applications, and per-tenant databases.turso.tech

I'd choose Turso over CockroachDB when I value simplicity and edge distribution more than a heavyweight relational/global-transaction model.

What about Neon?

Neon is my choice if the requirement is really “I want serverless PostgreSQL” rather than “I need a globally distributed database.”

It's an excellent developer experience, but a globally distributed CockroachDB deployment is a fundamentally different architecture.

---

My recommendation

Choose based on this decision tree:

• 🌎 Global users + globally distributed reads/writes + strong consistency → CockroachDB
• ⚡ Cloudflare Workers + read-heavy global app → D1
• 🪶 SQLite-compatible edge/local-first application → Turso
• 🐘 You specifically want PostgreSQL + serverless scaling → Neon
• 🐬 You specifically want MySQL/Vitess → PlanetScale

One important architectural point: don't optimize for “database latency” in isolation. If your API runs in Virginia and your database is in Virginia, putting read replicas around the world doesn't magically make a write from Tokyo fast. For a truly global application, you want compute + database locality together.

If you tell me your app type (SaaS, social, ecommerce, AI, etc.), expected traffic, and whether you need Postgres/MySQL/SQLite, I can narrow this down to one choice and give you a concrete architecture.