Kevin Åberg Kultalahti's avatar
Kevin Åberg Kultalahti me@kevinak.se 2 months ago
A proper SQLite database shouldn't have issues with this amount of traffic. D1 isn't just SQLite though, it's SQLite + an API. I would try using SQLite-in-DO instead of using D1. There's a good blog post about it here:
The Cloudflare Blog
Zero-latency SQLite storage in every Durable Object
Traditional cloud storage is inherently slow because it is accessed over a network and must synchronize many clients. But what if we could instead ...
 Secondly I would look at splitting up the database into multiple databases.
↑ Parent

Replies (2)

Luxas's avatar
Luxas _@end.the.fed.wtf 2 months ago
Yes, am already using SQLite-in-DO for subscription management with the Websocket Hibernation API. As visitors are geo-steered towards a regional DO. But I haven’t tested trying to handle the data independently across all of the DOs instead of a single D1, but I think that would add some serious latency and make it unnecessarily complex. I did just rollout an update that adds Cloudflare Queues to all EVENT messages, which should help write throughout and handle burst up to 5000/sec.
2 replies ↓
↑