A"Durable Objects guarantee global uniqueness, so once we depend on Durable Objects, routing HTTP requests is easy: just send them to the D1 Durable Object."
AA
CIs the D1 database file stored in a Durable Object or vice versa? The blog states:Durable Objects are a building block. D1 runs on Durable Objects.
"Durable Objects guarantee global uniqueness, so once we depend on Durable Objects, routing HTTP requests is easy: just send them to the D1 Durable Object."
does anyone know more about the routing process? It seems similar to a DNS or load-balancing process, so how exactly do we locate where the Durable Object is?
running_in_region │ ENAM . A specific machine in a specific colo/data center runs your DB as a Durable Object, which is just a V8 Isolate/single thread. There's a community site which identifies all of the colos that are used for a specific region: https://where.durableobjects.live/region/enam. Your D1 Db will never switch regions, but may switch colo/machine (machine issues, migration, etc). I am very curious about this. In a serverless environment, is a connection pool necessary? Or can we maintain connections between (user workers running workerd) and (D1 workers running workerd)?Connection pool not necessary and with Workers not really doable either, with how often they are created/destroyed. From what they've said before in here, just a request from the user worker -> d1 worker -> d1 durable object is my understanding. Workerd is open source, you can see the implementation (to a degree, can see sqlite is accessible internally for them on d1 storage's class -> sql). There was talk about giving Durable Objects access to an Sqlite db a while ago.
My guess is that SQLite is wrapped by workerd, providing APIs (bindings) to upper-level workers, and that D1 runs as some kind of worker to provide RESTful APIs or handle other tasks.
A
H
HHH
B
FFV
Rows read is so big after using an index.15,932 is the total number or rows in the table - 
V
SV
J
JV
D1_ERROR: D1 is overloaded. Requests queued for too long
C
HCHHCH
CV
.
I.VA
J
S
. Maybe enable GitHub sponsorships? For the actu...
I
IS
IV
Accounts is the main table with foreign key in all other tables, so when a customer delete an account it freeze everything. 
F
SAny suggestions?
SVEXPLAIN QUERY PLAN on all tables
running_in_region │ ENAMRows read15,932Select * from Jobs where status = 'scheduled' and scheduled_at <= datetime('now')CREATE INDEX if not exists scheduled_jobs_search ON Jobs (scheduled_at, status);CREATE INDEX if not exists scheduled_jobs_search ON Jobs (status,
scheduled_at);D1_ERROR: D1 is overloaded. Requests queued for too longDelete from Accounts where account_id = ?AccountsEXPLAIN QUERY PLAN