It's hard to maintain a large mysql cluster for the edge. Even if they do, the price will be as high
It's hard to maintain a large mysql cluster for the edge. Even if they do, the price will be as high as everest
TIn my case, D1, KV and R2 is perfectly fit. Most of the time my request are pagination, filtering with some predefined selected columns and get by ID. In mysql I will need a DB proxy to reduce the connections created and cache requests. With D1, it's not really faster but it's much cheaper without the worrying of connection managing and query caching.
Tyeah there are no dynamic binding yet
Tbut having a 50k warming database at the same time is mindblown
MLooks like we still need to manually configure database IDs in a global wrangler file as there’s no programmatic way to manage a fleet of D1 instancesYeah, dynamic bindings hasn't shipped yet, there's an unofficial package to automate the HTTP API steps you'd need to do atm though https://github.com/nora-soderlund/cloudflare-dynamic-bindings
Mwhat does D1 per DO mean
HSQLite Storage Bindings for DOs?
Mnot sure, unrelated work
MYou aren't going to get D1's in DO though, you'd get a raw sqlite instance
HWould the SQLite instance support replication?
HThat would be metal...
Monly if DO itself did
HAren't they two different storage systems?
HOr...
Mthink of D1 as the opinionated way to build a database service on top of raw sqlite+DO
HOr something like Code Procedures?
HOr whatever that "Colocate-your-code-next-to-D1" thing was called
M?
Moh you're asking if DO will support things we announced for D1
Mno idea
HIn one of the earlier blog posts for D1, there was something talking about being able to colocate some code next to a D1 instance. Not sure if that is actually a DO, or Service Binding, or something else
JTrying to determine if D1 is right for a current project...
For use cases where the size of a single table could grow quite large (think hundreds of thousands of rows), is D1 simply not a good option due to the 10GB limit?
For use cases where the size of a single table could grow quite large (think hundreds of thousands of rows), is D1 simply not a good option due to the 10GB limit?
Mwe have dbs with millions of rows, no dramas
Jthis is reassuring to hear... so basically I shouldn't ever have to worry about it (assuming i go with a per-user approach).
Jfor the dbs with millions of rows, what's the approximate size?
Ji've seen postgres dbs at 300 to 400 GB... that's my only context for this... maybe sqlite is inherently smaller or something?
M2ish GB
MWorkers also supports big classic postgres DBs - using Hyperdrive
JThis is all very helpful. Thank you.
Yeah, no base64 images or anything, mostly just simple String and such.
Yeah, no base64 images or anything, mostly just simple String and such.
Mwe picked sqlite particularly because we could load millions of dbs across the world really quickly - that pattern breaks down for extremely large, monolith-style DBs
Jmakes sense... trying to work with 300-400 GB DBs is also just flat-out painful...
J(from my experience at least)
Athis makes sense, thanks
Ais there a guide on setting up d1 with prisma edge in local development?
MCloudflare Docs
Prisma ORM is a next-generation JavaScript and TypeScript ORM that unlocks a new level of developer experience when working with databases thanks to …
RI recently tried D1 and i had bad results (wall times exploded). Worked fine with KV however so looking at possible alternatives. I built a reverse proxy that needs to be sync with a database from time to time. Interested about your experiences
Ai dont understand this part, in next you access the env through process.env, so how do you initialize the prisma client?
Afor context
Aoh
Jreally looking forward to this hopefully one day not being a limitation
Mmy workaround is a separate worker - locally use the localhost URL, in prod, use that workers prod URL
Aso if i understand correctly workers are their own thing and pages is its own thing, next-on-pages specifically is pages but it turns routes into workers ?
HIs the 
Maximum bound parameters per query limit of 100 going to be increased eventually? Just ran into a bug with Prisma, because that affects basically every query with relations as soon as you have more than 100 rows in a table Ahas anybody set up a next-pages app with D1 & Prisma? would love to see how you set up a basic route to read the request.env because i cant at all
NCloudflare Docs
Prisma ORM is a next-generation JavaScript and TypeScript ORM that unlocks a new level of developer experience when working with databases thanks to …
A
A
M@Nob I was trying this evening to get Prisma.io with D1 working.
Locally (wrangler dev) it works for me, but when deploying to CF my build starts failing...:
Before adding Prisma I did several deployments without any issue.
Not sure what is going wrong, logs are not telling much unfortunately...
Locally (wrangler dev) it works for me, but when deploying to CF my build starts failing...:
Before adding Prisma I did several deployments without any issue.
Not sure what is going wrong, logs are not telling much unfortunately...
