Will it be a good idea to start building an application with d1 now? Or should we use other dbs?

CCodename_404 Will it be a good idea to start building an application with d1 now? Or should w...

D

Dahoom•8/7/23, 3:24 AM

I would say test it right now. If you decide its not for you, then you can easily switch to another database with little refactoring since its just regular sql commands

D

Dahoom•8/7/23, 3:25 AM

The main upside with it is the setup with workers and pages functions is painless

L

LeftSpace•8/7/23, 3:32 AM

beta engine looks scary tho you don't have dump or download backup

L

LeftSpace•8/7/23, 3:32 AM

Im still using alpha

L

LeftSpace•8/7/23, 3:35 AM

just tested if we can migrate from alpha to beta,yeah it works i'll move to beta when its safer to use

L

LeftSpace•8/7/23, 3:42 AM

if anyone looking for migrate alpha to beta engine here's what i did

/*update your wrangler first*/
>> wrangler update
npm install -g wrangler

>> create new db with beta engine
wrangler d1 create dbname

/*you can use your sqlite3 if you want I had xampp already so*/
make sure to run as admin
C:\xampp\MercuryMail\sqlite3.exe "backup-file-from-cf.sqlite3"
>> sqlite
.output c:/backup.sql
.dump
.exit

>> wrangler
wrangler d1 execute dbname --file="c:\backup.sql"

/*update your wrangler first*/
>> wrangler update
npm install -g wrangler

>> create new db with beta engine
wrangler d1 create dbname

/*you can use your sqlite3 if you want I had xampp already so*/
make sure to run as admin
C:\xampp\MercuryMail\sqlite3.exe "backup-file-from-cf.sqlite3"
>> sqlite
.output c:/backup.sql
.dump
.exit

>> wrangler
wrangler d1 execute dbname --file="c:\backup.sql"

/*update your wrangler first*/
>> wrangler update
npm install -g wrangler

>> create new db with beta engine
wrangler d1 create dbname

/*you can use your sqlite3 if you want I had xampp already so*/
make sure to run as admin
C:\xampp\MercuryMail\sqlite3.exe "backup-file-from-cf.sqlite3"
>> sqlite
.output c:/backup.sql
.dump
.exit

>> wrangler
wrangler d1 execute dbname --file="c:\backup.sql"

/*update your wrangler first*/
>> wrangler update
npm install -g wrangler

>> create new db with beta engine
wrangler d1 create dbname

/*you can use your sqlite3 if you want I had xampp already so*/
make sure to run as admin
C:\xampp\MercuryMail\sqlite3.exe "backup-file-from-cf.sqlite3"
>> sqlite
.output c:/backup.sql
.dump
.exit

>> wrangler
wrangler d1 execute dbname --file="c:\backup.sql"

LLeftSpace beta engine looks scary tho you don't have dump or download backup

B

Bulbasaur•8/7/23, 4:54 AM

agreed, though time travel for normal usecases of restoring if there's issues is great, definitely still want a first-party way to dump and download a backup!

L

LeftSpace•8/7/23, 5:19 AM

imagine what will happen if you wanted to move to somewhere else

L

LeftSpace•8/7/23, 5:20 AM

since there's no download backup!

D

Dahoom•8/7/23, 10:40 AM

Perfect, it even retains the comments and indexes

D

Dahoom•8/7/23, 10:40 AM

Thank you

C

Codename_404OP•8/7/23, 12:34 PM

is there any maximum table limit on d1 alpha?

Original message was deleted

M

Matt Silverlock•8/7/23, 2:32 PM

Typically an empty table is about 4KB

S

samratarmas•8/7/23, 8:06 PM

Hello team, is the 10 database limit for D1 only temporary during beta? If not, is there any fundamental reason to have this limit in place?

S

samratarmas•8/7/23, 8:11 PM

And second question, is js transactions for d1 a planned feature that is on the pipeline or is durable objects the way to do transactions

Ssamratarmas Hello team, is the 10 database limit for D1 only temporary during beta? If not, ...

M

Matt Silverlock•8/7/23, 9:24 PM

Paid users will be able to create more databases once we hit beta.

Ssamratarmas And second question, is js transactions for d1 a planned feature that is on the ...

M

Matt Silverlock•8/7/23, 9:24 PM

Search "transactions" here in chat

G

Greg•8/8/23, 4:12 AM

my worker seems to start throwing an error as soon as I add the D1 config to my wrangler.toml:

[[d1_databases]]
binding = "DB"
database_name = "<DATABASE_NAME>"
database_id = "<unique-ID-for-your-database>"

[[d1_databases]]
binding = "DB"
database_name = "<DATABASE_NAME>"
database_id = "<unique-ID-for-your-database>"

[[d1_databases]]
binding = "DB"
database_name = "<DATABASE_NAME>"
database_id = "<unique-ID-for-your-database>"

[[d1_databases]]
binding = "DB"
database_name = "<DATABASE_NAME>"
database_id = "<unique-ID-for-your-database>"

It's a TypeError:

[mf:err] TypeError: head is not a function

[mf:err] TypeError: head is not a function

[mf:err] TypeError: head is not a function

[mf:err] TypeError: head is not a function

G

Greg•8/8/23, 4:16 AM

I'm just running

wrangler dev

wrangler dev

then opening localhost, this is the error

C

cyan•8/8/23, 10:19 AM

Is provisioning a db (primary, non replicated) for each user a stupid idea? Is D1 designed for this?
The database size limit would make sense with this model as 1gb is plenty for each user (but not enough for multiple).
Latency would also be fantastic while keeping consistency intact.

Ccyan Is provisioning a db (primary, non replicated) for each user a stupid idea? Is D...

D

Dahoom•8/8/23, 10:23 AM

Theres currently a limit of 10 dbs, https://developers.cloudflare.com/d1/platform/limits/
I would say create a table for each user but that aswell might not be the best idea, since each table does take extra space as skye said

Limits · Cloudflare D1 docs

Many of these limits will increase during D1’s public alpha. Join the #d1-open-alpha channel in the Cloudflare Developer Discord to keep up to date …

D

Dahoom•8/8/23, 10:25 AM

maybe talk with decide.gg to help design a database schema for your use case, thats what i do

R

rotator•8/8/23, 10:26 AM

Hey, I'm trying to compare pricing of D1 vs Durable Objects Transactional Storage API (on the $5 plan):

D1: 25,000 mil 4 KB reads included = $0
DO: 1 mil 4KB reads included, then (24,999 mil * $0.2/mil) = $4,999

That's just the free allowance, the base price for reads is also 200x. Writes are the same base price, but the free allowance of D1 alone will cost 49$ for Durable Objects. Am I missing something here? My use case could fit both, but the pricing is encouraging me to use Workers+D1 or replace the storage of DO with D1.

DDahoom Theres currently a limit of 10 dbs, https://developers.cloudflare.com/d1/platfor...

C

cyan•8/8/23, 10:27 AM

thanks!

Rrotator Hey, I'm trying to compare pricing of D1 vs Durable Objects Transactional Storag...

D

Dahoom•8/8/23, 10:31 AM

I would recommend d1 but its still in alpha and there are current caps/limitations, to me the best thing is its just sql so easy to intigrate and build with

D

Dahoom•8/8/23, 12:03 PM

Does anyone have an example worker/function using the query JSON api? I'm having a hard time getting a grasp of it from the docs

D

Dahoom•8/8/23, 12:23 PM

anything really

D

Dahoom•8/8/23, 12:24 PM

but prepared would be preferrable

DDahoom I would recommend d1 but its still in alpha and there are current caps/limitatio...

C

chientrm.com•8/8/23, 12:24 PM

D1 is based on Sqlite so that migration is not really an issue.

Original message was deleted

C

Cyb3r-Jak3•8/8/23, 12:28 PM

There is not. D1 is primarily for workers.

Original message was deleted

C

chientrm.com•8/8/23, 12:29 PM

You can use this package to run a D1 proxy and using D1 from your PHP https://www.npmjs.com/package/cf-workers-proxy

npm

cf-workers-proxy

Enable Cloudflare Workers runtime for local development. Latest version: 0.3.0, last published: 17 days ago. Start using cf-workers-proxy in your project by running

npm i cf-workers-proxy

npm i cf-workers-proxy

npm i cf-workers-proxy

npm i cf-workers-proxy. There are no other projects in the npm registry using cf-workers-proxy.

C

chientrm.com•8/8/23, 12:30 PM

nvm the package is js-only

D

Dahoom•8/8/23, 12:31 PM

you can do a makeshift API with cloudflare workers and call it within php

D

Dahoom•8/8/23, 12:32 PM

since the worker will be connected to d1 you could set a secret env variable with an API key, authenticate through the bearer header and pass in sql strings to be executed

D

Dahoom•8/8/23, 12:35 PM

I've done similar but it was in php for cloudflare pages, as long as you write the token validation correctly everything should be smooth

D

Dahoom•8/8/23, 12:36 PM

I've never tried firebase but probably?

Original message was deleted

C

Cyb3r-Jak3•8/8/23, 12:44 PM

The D1 API is not public and if it does become public it will fall under the API rate limit. Making a worker to proxy is your best bet

Ccyan Is provisioning a db (primary, non replicated) for each user a stupid idea? Is D...

G

GuillaumeLakano•8/8/23, 12:46 PM

It's not a stupid idea, and it's add a strong security layer, it's currently what we doing with DO ( a mini DB for each user ) and we wait about the same possibility in D1
D1 is based on DO, DO have unlimited Objects, and D1 will increase from 10 databases per account to « thousands to tens of thousands of tenants » , but it's still not enough if you have (expect) more users than this limit.

EDIT: I've said « D1 is based on DO » because I've read that here before, but Matt add this precisions: d1-database

GGuillaumeLakano It's not a stupid idea, and it's add a strong security layer, it's currently wha...

M

Matt Silverlock•8/8/23, 1:40 PM

We haven’t communicated any upper bound. We just have limits during alpha.

MMatt Silverlock We haven’t communicated any upper bound. We just have limits during alpha.

G

GuillaumeLakano•8/8/23, 2:00 PM

So, may be I've misunderstood you ( « We have some ideas here for the “thousands to tens of thousands of tenants” - that will isolate each DB you create. Can’t share more yet and won’t be “next month”. » in d1-database )

G

GuillaumeLakano•8/8/23, 2:02 PM

could be really useful if CF can officially claims this will be unlimited, so this means we can start new project, using D1 directly ( while it's in development period, until the stable release of D1 one day )

GGuillaumeLakano could be really useful if CF can officially claims this will be unlimited, so th...

M

Matt Silverlock•8/8/23, 2:40 PM

We at least anticipate “tens of thousands” by the end of the year. I’m not in the habit of making claims that we haven’t tested but there are no architectural reasons why millions will not work.

GGuillaumeLakano could be really useful if CF can officially claims this will be unlimited, so th...

M

Matt Silverlock•8/8/23, 2:41 PM

If it’s easier I can just say “eventually unlimited”. If you have millions of users we will make it work. One of the reasons we built Workers for Platforms.

G

GuillaumeLakano•8/8/23, 2:59 PM

Awesome, thank you @Matt for theses precisions!

R

rotator•8/8/23, 3:41 PM

Any comment regarding this? d1-database
To rephrase: if D1 is built on top of DO, then why is it so much cheaper?

Interestingly enough, I can wrap my D1 calls into DO transactions like that and it seems to work fine

    const value = 0;
    let d1Response: any;
    await this.state.storage.transaction(async (txn) => {
      try {
        txn.put('value', this.value);
        const stmt = this.db
          .prepare(`INSERT INTO items (itemData) VALUES (?) RETURNING *`)
          .bind(JSON.stringify({ value }));
        d1Response = await stmt.all();
      } catch (e) {
        console.error(e);
        txn.rollback();
        throw e;
      }
    });

    const value = 0;
    let d1Response: any;
    await this.state.storage.transaction(async (txn) => {
      try {
        txn.put('value', this.value);
        const stmt = this.db
          .prepare(`INSERT INTO items (itemData) VALUES (?) RETURNING *`)
          .bind(JSON.stringify({ value }));
        d1Response = await stmt.all();
      } catch (e) {
        console.error(e);
        txn.rollback();
        throw e;
      }
    });

    const value = 0;
    let d1Response: any;
    await this.state.storage.transaction(async (txn) => {
      try {
        txn.put('value', this.value);
        const stmt = this.db
          .prepare(`INSERT INTO items (itemData) VALUES (?) RETURNING *`)
          .bind(JSON.stringify({ value }));
        d1Response = await stmt.all();
      } catch (e) {
        console.error(e);
        txn.rollback();
        throw e;
      }
    });

    const value = 0;
    let d1Response: any;
    await this.state.storage.transaction(async (txn) => {
      try {
        txn.put('value', this.value);
        const stmt = this.db
          .prepare(`INSERT INTO items (itemData) VALUES (?) RETURNING *`)
          .bind(JSON.stringify({ value }));
        d1Response = await stmt.all();
      } catch (e) {
        console.error(e);
        txn.rollback();
        throw e;
      }
    });

but I wouldn't want to do this just for cost management purposes

Rrotator Any comment regarding this? https://discord.com/channels/595317990191398933/9920...

M

Matt Silverlock•8/8/23, 3:56 PM

I've never said it's built on top of DO. How they store data is entirely distinct.

M

marko•8/8/23, 4:17 PM

I'm testing D1 and I followed the comments API example but I'm getting

no such table

no such table

no such table

no such table error.

wrangler d1 info

wrangler d1 info

wrangler d1 info

wrangler d1 info shows table count correctly. Any ideas what I'm doing wrong?

MMatt Silverlock I've never said it's built on top of DO. How they store data is entirely distinc...

R

rotator•8/8/23, 4:22 PM

I see, thanks for clarifying this.

I can infer that for overlapping use cases D1 is heavily encouraged, unless prices change before D1 is generally available.

Mmarko I'm testing D1 and I followed the comments API example but I'm getting `no such ...

M

marko•8/8/23, 4:32 PM

Just noticed that

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote works, so I'm guessing that this is related to local env.

Will it be a good idea to start building an application with d1 now? Or should we use other dbs?

Similar Threads

Similar Threads

Similar Threads