This is how I decide: large blobs?: R2 key value?: DOs SQL?: D1 KV: almost never <:LUL:5846028625589
This is how I decide:
large blobs?: R2
key value?: DOs
SQL?: D1
KV: almost never
large blobs?: R2
key value?: DOs
SQL?: D1
KV: almost never
HKV: Large-Scale Key-Value(100+ rps)
HEspecially if requests come from different colos
UI would still use DOs for 100+ rps just with cache in front. Pretty much the only case I would use KV atm is a session store instead of creating a DO and using cache for that 
JKV is fantastic and I would always recommend it for read-heavy operations. If you need global durability then of course DOs and things like that are gonna be better, but if you don't (like so many use-cases), KV's simplicity and pricing is incredible.
Jyep
HDepends. The DO could be in the same colo, and then you probably won’t get much, if any, difference
HAnd that all depends on caching, which you can do against a DO too
HTL;DR, KV and DOs are two pretty different products, and thus neither is a one size fits all solution. Use your own judgements, and try to run the math yourself if you want
IAre you using the new backend?
BI noticed is that it is throwing CORS issue when I sent in fetch body, a text when database schema is expecting number like ' phone:"abc" ' instead of 'phone:123' , which should as per me should be database error, not cors error. Is it common ?
ICan you ensure you are on the latest Wrangler version?
ICheck
wrangler --version, it should be 3.0.0 or higher
JI'm really struggling to bind my worker script to D1. I've seen in the documention that I need to "add the following to the end of your wrangler.toml", but I can't see any instructions how exactly to do that (or even what a wrangler.toml file is). Is it something local on my computer? Is it hosted on Cloudflare somewhere?
IWrangler.toml is a file that controls how your Worker is deployed and what it can access. https://developers.cloudflare.com/workers/wrangler/configuration/
JRight, I've seen that
IThis step here shows how to add D1 to your wrangler.toml
JCan you please point to the page where it shows how to edit / save / upload the wranger.toml?
MWrangler optionally uses a wrangler.toml configuration file to customize the development and publishing setup for a Worker.
MWhen you call
wrangler init as you follow the guide it is created for youM
MRun this end to end, in full, @jpony - https://developers.cloudflare.com/d1/get-started/#1-install-and-authenticate-wrangler
MLet us know where you specifically get stuck after you / as you work through it. Don’t skip any parts 
SWhen trying to run the D1 Drizzle sample I receive an error: SqliteError: no such table: articles. In the web console I can see the table, without any entries. Any idea on how I can identify the root cause?
MAre you running the sample locally, using
wrangler dev- ? Can you confirm the DB is the same?
SYes, would say so.
So that would seem okay to me as well.
context.DB isSo that would seem okay to me as well.
J@elithrar Ah ok I understand now, I need to set it up all locally to make it work.
JHopefully in the future we can configure D1 like you can with worker key values from the web interface! (but I understand doing it this way during the alpha, since it seems like you automatically add a bunch of code to the worker script to make it work properly)
MIs this being run locally?
SStupid me... example is on Wrangler 2.15, I used 3. Will revert back to 2.15 as used in the sample. Therefor yes...
JSo I was able to bind my DB to my worker script. Is there a good page with example queries? Basically I want to run this from my worker script: SELECT * FROM DB_BIND WHERE name LIKE %city% LIMIT 10; then output the results in json, or false if it doesn't find anything.
JSadly chat GPT doesn't understand D1 yet 
JI tried this but it doesn't work:
try {
const result = await CITIES_ALL.prepare(
return new Response(JSON.stringify(result), {
status: 200,
headers: {...headers, 'Content-Type': 'application/json'}
});
} catch (error) {
return new Response(JSON.stringify({ error: 'Error' }), {
status: 500,
headers: {...headers, 'Content-Type': 'application/json'}
});
}
try {
const result = await CITIES_ALL.prepare(
select * from cities_all where name like ? limit 10
).bind('%' + sanitizedCity + '%').all()return new Response(JSON.stringify(result), {
status: 200,
headers: {...headers, 'Content-Type': 'application/json'}
});
} catch (error) {
return new Response(JSON.stringify({ error: 'Error' }), {
status: 500,
headers: {...headers, 'Content-Type': 'application/json'}
});
}
JThe error I get is "ReferenceError: CITIES_ALL is not defined", so I perhaps I am not initializing it properly? I got this message when I published it, so I think I must be part of the the way there: Your worker has access to the following bindings:
- D1 Databases:
- CITIES_ALL: cities_all xxxx
Dyou're trying to access it as
CITIES_ALL, which is the syntax for service workers - the new module worker syntax makes bindings available under envenv.CITIES_ALLJI tried env.CITIES_ALL as well, and it got the same error:
'ReferenceError: env is not defined'
'ReferenceError: env is not defined'
Dcan you show your worker code?
Dyou're using service worker syntax, which doesn't work with D1 - here's how to migrate: https://developers.cloudflare.com/workers/learning/migrating-to-module-workers/#migrating-to-module-workers
This guide will show you how to migrate your Workers from the Service Worker syntax to the new Module Worker format.
JAh, ok thanks for that. I'll take a look!
JHmmm, maybe I am misunderstanding something and the database is only available locally?
JI probably should wait until D1 is out of alpha anyway before I continue tinkering with it. Thank you for your help!
Bhow do i bind d1 to a worker, i need a basic backend and db for my school project :p
