is D1 distributed as well? I think I remember reading somewhere that it's not and is instead deployed to the closest datacenter to where you're initiating it, but I can't find it now, and now I wonder if I had dreamt this or something
I want to create a new DB for each client, I guess best way it is to use CF API (https://developers.cloudflare.com/api/operations/cloudflare-d1-create-database). But then how could I dynamically query the selected DB from the worker? (I don't want to query via API, but somehow bind it dynamically if it's possible)
yep, it's what I've done as explained in the message, but I always receive the same error. I've tried to do a GET of full settings and then to inject the new bindings, and to apply with a PATCH ( in form-data ) I've also tried to only PATCH the settings object with only the 'bindings' array inside The only things working is if I'm creating a new binding with only one entry, but all previous are destroyed ( and from a HTTP PATCH philosophy, this should be better to only PATCH and not replace like a HTTP PUT )
Anyone has experience with https://github.com/renoki-co/l1? Does it work "just as a wrapper" where migrations, models, eloquent etc from Laravel is still available ?
D1 is in beta, which means, "It's gonna break y'all" so do not make this mission critical. While it sucks, it also means that every other service is in front of it regarding restoration.
The said that the issue was a power outage, I am guessing that they have to restore from full backup and the adjust configurations.
I can only imagine the size of a cloudflare backup.
May be the series law But the good point is, each time, the staff take time to create a blog article to explain why, to explain how they fix it to prevent this happening again. Nothing is never perfect, but at least, they're transparent and try to improve each time on theses outages
guess it's just bad luck, we've been using Cloudflare on many products we've build and it's been really stable but this week is just bad luck, and this incident is a different magnitude
To prevent to have a huge table of stats that growing everyday, we want after each day (or may be hour) to move the rows from the main table to a new dynamically created table « archive_stats_YYMMDD », but we don't known if we'll reach a D1 limit at some points.
Many of these limits will increase during D1’s public beta. Join the #d1-beta channel in the Cloudflare Developer Discord or subscribe to D1’s public …