i need to use durable objects

KKWAC i need to use durable objects

B

Blind Goose•1/15/25, 4:40 PM

Then use them in your API, what exactly are you asking for help with?

K

KWACOP•1/15/25, 4:41 PM

I just want to see example god damn

B

Blind Goose•1/15/25, 4:41 PM

An example, of what, I showed you an example of how to do websockets in Nuxts

B

Blind Goose•1/15/25, 4:41 PM

And how to use the web sockets for workers api

KKWAC how do I set it up in the api

K

KWACOP•1/15/25, 4:41 PM

.

K

KWACOP•1/15/25, 4:43 PM

I found this but im not sure if it's good example

https://github.com/nicgene/nuxt-durable-object

GitHub

GitHub - nicgene/nuxt-durable-object

Contribute to nicgene/nuxt-durable-object development by creating an account on GitHub.

B

Blind Goose•1/15/25, 4:44 PM

I would start there.

K

KWACOP•1/15/25, 4:59 PM

thank you sir for your help, i really appreciate it

C

Chris Jayden•1/15/25, 5:23 PM

Some methods on my stub are being returned as

never

never

never

never. Anyone had this before?

G

Gagan Suie•1/15/25, 6:44 PM

hi, is there a way to do text search in DO storage?

GGagan Suie hi, is there a way to do text search in DO storage?

H

Hard@Work•1/15/25, 6:48 PM

Via FTS5: https://developers.cloudflare.com/d1/sql-api/sql-statements/#supported-sqlite-extensions

Cloudflare Docs

SQL statements · Cloudflare D1 docs

D1 is compatible with most SQLite's SQL convention since it leverages SQLite's query engine. D1 supports a number of database-level statements that allow you to list tables, indexes, and inspect the schema for a given table or index.

H

Hard@Work•1/15/25, 6:48 PM

That's the D1 docs, but it should

work with DOSQLite too

HHard@Work That's the D1 docs, but it should™️ work with DOSQLite too

G

Gagan Suie•1/15/25, 6:49 PM

even in the do chat sample? https://github.com/cloudflare/workers-chat-demo

GitHub

GitHub - cloudflare/workers-chat-demo

Contribute to cloudflare/workers-chat-demo development by creating an account on GitHub.

G

Gagan Suie•1/15/25, 6:50 PM

i dont think its using DOSQLite

GGagan Suie even in the do chat sample? https://github.com/cloudflare/workers-chat-demo

H

Hard@Work•1/15/25, 6:51 PM

No, you would probably have to migrate it to SQLite

J

jd•1/15/25, 7:54 PM

Hi! Question: I'm looking for a place to store 2-10T of our model training image / video data that doesn't incur crazy monthly or egress fees, flexible with multiple cloudproviders.

Most importantly, great with large file download performance like .tar file / webdataset or large # of small files if needed.

How cloudflare storage performs in terms of benchmark?

Datapoint: Our model weights live on huggingface and with their cli + hf_transfer we can get 1.2G/s download speed on EC2.

Thanks!

Jjd Hi! Question: I'm looking for a place to store 2-10T of our model training image...

L

lambrospetrou•1/15/25, 8:18 PM

Check Cloudflare R2, which is S3-compatible object storage and has zero egress fees.

J

jd•1/15/25, 10:19 PM

Yep i was just curious about R2's performance on large file IO. Let me run some benchmarks on my own then

J

jd•1/15/25, 10:24 PM

:insane: sorry i didn't see there's a r2 channel and thought this one was

1

1984 Ford Laser•1/16/25, 2:23 AM

Anyone else having issues with websockets not hibernating? Some code that was working fine a few weeks ago is now no longer hibernating the connections

1

1984 Ford Laser•1/16/25, 2:28 AM

Hmm seems to be localized to a specific namespace, tried a different DO and that one is fine

1

1984 Ford Laser•1/16/25, 3:36 AM

Okay this is a dumb one, I think I fixed it. On top of the normal

message

message

message

message and

close

close

close

close WS handlers, I also had a

error

error

error

error one set up, which was supposed to remove the current connection from the list of connections, but wasn't necessarily closing the connection, such as if the client experienced an error, but not one that caused the socket to close. Somewhere, this was causing the socket to stay open or something. You can see a comparison in the screenshots

HHard@Work That's the D1 docs, but it should™️ work with DOSQLite too

G

Gagan Suie•1/16/25, 7:53 AM

does DOSQLite create a new table for every DO session? or do all connections share the same DB table?

GGagan Suie does DOSQLite create a new table for every DO session? or do all connections sha...

1

1984 Ford Laser•1/16/25, 8:52 AM

Tables per instance

K

KWACOP•1/16/25, 12:49 PM

Property 'idFromName' does not exist on type 'DurableObject'.
Property 'get' does not exist on type 'DurableObject'.

Property 'idFromName' does not exist on type 'DurableObject'.
Property 'get' does not exist on type 'DurableObject'.

Property 'idFromName' does not exist on type 'DurableObject'.
Property 'get' does not exist on type 'DurableObject'.

Property 'idFromName' does not exist on type 'DurableObject'.
Property 'get' does not exist on type 'DurableObject'.

export default defineEventHandler(async (event) => {
    try {
        const env = event.context.cloudflare?.env.DUMMY_OBJECT;
        const id = env.idFromName('counter');
        const stub = env.get(id);
        const response = await stub.fetch(event.context.cloudflare.request);
        const data = await response.json() as { value: number };
        return data;
    }
    catch (error) {
        console.error(error);
        return { error: 'Failed to fetch from Durable Object' };
    }
});

export default defineEventHandler(async (event) => {
    try {
        const env = event.context.cloudflare?.env.DUMMY_OBJECT;
        const id = env.idFromName('counter');
        const stub = env.get(id);
        const response = await stub.fetch(event.context.cloudflare.request);
        const data = await response.json() as { value: number };
        return data;
    }
    catch (error) {
        console.error(error);
        return { error: 'Failed to fetch from Durable Object' };
    }
});

export default defineEventHandler(async (event) => {
    try {
        const env = event.context.cloudflare?.env.DUMMY_OBJECT;
        const id = env.idFromName('counter');
        const stub = env.get(id);
        const response = await stub.fetch(event.context.cloudflare.request);
        const data = await response.json() as { value: number };
        return data;
    }
    catch (error) {
        console.error(error);
        return { error: 'Failed to fetch from Durable Object' };
    }
});

export default defineEventHandler(async (event) => {
    try {
        const env = event.context.cloudflare?.env.DUMMY_OBJECT;
        const id = env.idFromName('counter');
        const stub = env.get(id);
        const response = await stub.fetch(event.context.cloudflare.request);
        const data = await response.json() as { value: number };
        return data;
    }
    catch (error) {
        console.error(error);
        return { error: 'Failed to fetch from Durable Object' };
    }
});

KKWAC ```Property 'idFromName' does not exist on type 'DurableObject'. Property 'get' ...

L

lambrospetrou•1/16/25, 1:04 PM

What framework is this? Those methods are on the DO Namespace type, not the

DurableObject

DurableObject

DurableObject

DurableObject type: https://developers.cloudflare.com/durable-objects/api/namespace/#idfromname
You probably have wrong types defined for

DUMMY_OBJECT

DUMMY_OBJECT

DUMMY_OBJECT

DUMMY_OBJECT.

K

KWACOP•1/16/25, 1:04 PM

nuxt

K

KWACOP•1/16/25, 1:04 PM

I updated to

DurableObjectNamespace

DurableObjectNamespace

DurableObjectNamespace

DurableObjectNamespace

/// <reference types="@cloudflare/workers-types/2023-07-01" />

declare module "h3" {
  interface H3EventContext {
    cf: CfProperties;
    cloudflare: {
      request: Request;
      // env: Env;
      env: {
        MY_KV: KVNamespace,
        DB: D1Database,
        MY_BUCKET: R2Bucket;
        DUMMY_OBJECT: DurableObjectNamespace;
      }
      context: ExecutionContext;
    };
  }
}

export {};

/// <reference types="@cloudflare/workers-types/2023-07-01" />

declare module "h3" {
  interface H3EventContext {
    cf: CfProperties;
    cloudflare: {
      request: Request;
      // env: Env;
      env: {
        MY_KV: KVNamespace,
        DB: D1Database,
        MY_BUCKET: R2Bucket;
        DUMMY_OBJECT: DurableObjectNamespace;
      }
      context: ExecutionContext;
    };
  }
}

export {};

/// <reference types="@cloudflare/workers-types/2023-07-01" />

declare module "h3" {
  interface H3EventContext {
    cf: CfProperties;
    cloudflare: {
      request: Request;
      // env: Env;
      env: {
        MY_KV: KVNamespace,
        DB: D1Database,
        MY_BUCKET: R2Bucket;
        DUMMY_OBJECT: DurableObjectNamespace;
      }
      context: ExecutionContext;
    };
  }
}

export {};

/// <reference types="@cloudflare/workers-types/2023-07-01" />

declare module "h3" {
  interface H3EventContext {
    cf: CfProperties;
    cloudflare: {
      request: Request;
      // env: Env;
      env: {
        MY_KV: KVNamespace,
        DB: D1Database,
        MY_BUCKET: R2Bucket;
        DUMMY_OBJECT: DurableObjectNamespace;
      }
      context: ExecutionContext;
    };
  }
}

export {};

K

KWACOP•1/16/25, 1:05 PM

my wrangler.toml should look like this?

[[durable_objects.bindings]]
name = "DUMMY_OBJECT"
class_name = "DummyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

[[durable_objects.bindings]]
name = "DUMMY_OBJECT"
class_name = "DummyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

[[durable_objects.bindings]]
name = "DUMMY_OBJECT"
class_name = "DummyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

[[durable_objects.bindings]]
name = "DUMMY_OBJECT"
class_name = "DummyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

KKWAC my wrangler.toml should look like this? ```toml [[durable_objects.bindings]] na...

L

lambrospetrou•1/16/25, 1:06 PM

Assuming your class extending

DurableObject

DurableObject

DurableObject

DurableObject is named

DummyDurableObject

DummyDurableObject

DummyDurableObject

DummyDurableObject then yes.

K

KWACOP•1/16/25, 1:08 PM

oh wait I don't have extending class

K

KWACOP•1/16/25, 1:08 PM

where do I define it in nuxt?

KKWAC where do I define it in nuxt?

L

lambrospetrou•1/16/25, 1:10 PM

I don't know nuxt, but you can put it anywhere so that when exported it can be in the final JS bundle you upload to Cloudflare.

J

Jacob Wright•1/16/25, 6:55 PM

I have 2 questions, if you could help.

for a DO to be deleted, I assume
```
storage.deleteAll()
```
storage.deleteAll()
```
storage.deleteAll()
```
storage.deleteAll()
must be called and no SQLite tables can exist?
I create my SQLite tables in the constructor, but if a DO is deleted with
```
storage.deleteAll()
```
storage.deleteAll()
```
storage.deleteAll()
```
storage.deleteAll()
, and a new call comes in after that, it errors because the tables don't exist, and I don't know whether to re-create them or not. Is there a solution to this?

JJacob Wright I have 2 questions, if you could help. 1. for a DO to be deleted, I assume `stor...

L

lambrospetrou•1/16/25, 6:59 PM

Yes. Once
```
deleteAll
```
deleteAll
```
deleteAll
```
deleteAll
is called everything is deleted, including all your tables.

[...] I don't know whether to re-create them or not. Is there a solution to this?

I don't understand the question. If you decided to delete all the data for a DO, why would you want to handle a request to it and re-create the tables?
If you want to gracefully fail the request, check if the tables exist when handling the request, and if not return the appropriate error. If you want incoming requests to still have their tables, why are you deleting them in the first place then?

Llambrospetrou 1. Yes. Once `deleteAll` is called everything is deleted, including all your tab...

J

Jacob Wright•1/16/25, 7:07 PM

In production, likely I won't, but in testing, I'm deleting the data and then testing again. I just had an idea though. I can set

this.#deleted = true

this.#deleted = true

this.#deleted = true

this.#deleted = true and then reinitialize the database on future requests. If the DO goes out of memory, the constructor will run again and initialize it. If it hasn't gone out of memory yet, #deleted will be true. Should work.

JJacob Wright In production, likely I won't, but in testing, I'm deleting the data and then te...

L

lambrospetrou•1/16/25, 7:08 PM

I have a feeling something is not understood. Why deleteAll if you are going to recreate them?

J

James•1/16/25, 7:22 PM

C

Chris Jayden•1/16/25, 9:04 PM

Lmao

Llambrospetrou I have a feeling something is not understood. Why deleteAll if you are going to ...

J

Jacob Wright•1/16/25, 10:41 PM

Testing. I'm clearing out the data between tests. The DO represents a single collaborative document (like a GDocs file) that stores all the changes and metadata for the document. I'm creating it, making changes, deleting it, then creating it again, making different changes, deleting it. You know, testing.

JJacob Wright In production, likely I won't, but in testing, I'm deleting the data and then te...

J

Jacob Wright•1/16/25, 10:42 PM

Using

this.#deleted

this.#deleted

this.#deleted

this.#deleted to track if the db needs to be re-created works great.

J

Jacob Wright•1/16/25, 11:42 PM

And my guess is if I have

/documents/:id

/documents/:id

/documents/:id

/documents/:id route to a SQLite DO that creates the schema in the constructor, then if a hacker were to spam my service with a bunch of

GET /documents/XXXXX

GET /documents/XXXXX

GET /documents/XXXXX

GET /documents/XXXXX calls trying to find a valid document, that every one of those invalid GETs would create a new DO that wouldn't be deleted because the SQLite database would be created simply by the act of accessing it, even if it returns a 404. Is that right?

With the old storage, accessing a DO without any data in it wouldn't cause a new DO to stick around. Unless data is actually stored in the storage, there is nothing that keeps it around after access.

Does anyone have strategies to preventing this behavior? Would the right way to do it be to create the database on first write (POST) and any GETs would check if the tables exist first and 404 if they don't. I suppose this create-db-on-write behavior would also solve the other issue above where I had to track if the DO was deleted. Thanks for letting me talk it out!

Is this a known best practice? Should the examples be updated to guide people to not create the database in the constructor since any access to a non-existent DO will create a new DB file that will stick around forever?

JJacob Wright And my guess is if I have `/documents/:id` route to a SQLite DO that creates the...

1

1984 Ford Laser•1/17/25, 12:02 AM

Have some sort of auth header or something, before accessing the DO, in the preceding Worker. Return before DO stub is every created

11984 Ford Laser Have some sort of auth header or something, before accessing the DO, in the prec...

J

Jacob Wright•1/17/25, 12:06 AM

That keeps non-authenticated users from hacking, but not authenticated users. There's some rule about never trusting users.

1

1984 Ford Laser•1/17/25, 12:07 AM

Pretty specific attack vector, hackers intercepting an authed users session? What is your use case exactly?

11984 Ford Laser Pretty specific attack vector, hackers intercepting an authed users session? Wha...

J

Jacob Wright•1/17/25, 12:12 AM

Oh, no, it is just that anyone can sign up for my service (just like anyone can get a Google account) and then they'd be authed as they tried to access documents. So the only difference is that the hacker would need a username/password before hacking.

My product is a novel writing tool (dabblewriter.com), and I'm switching over from the DO kv storage to SQLite. It's pretty awesome so far. But this ... hole? I guess ... in how the SQLite DOs work stumped me. I could not worry about it for now, but I wanted to see if there has been any thought to doing this the Right Way™ and what that might be. And I'm not sure about in the colos, but locally the SQLite file gets created even if .sql.exec() is called at all, so I'm not sure if there is a way to keep DOs from hanging around if no data has been added to it.

Thanks for your suggestions @1984 Ford Laser! I appreciate the help.

1

1984 Ford Laser•1/17/25, 12:15 AM

You might wanna implement some sort of rate limiter (of which there are examples in the docs) so that users can't spam APIs. There is no right way usually with CF's stuff, you're left to your own devices. For someone's use case, creating a new db table with every constructor might be perfectly necessary. The rate limiter could also signal to you when someone is attempting to abuse the system and you can act accordingly. I am having similar thought exercises as I start to build out a proof of concept into a commercially sellable product based on DOs, trying to figure things like how to bill a customer based on DO usage for example

11984 Ford Laser You might wanna implement some sort of rate limiter (of which there are examples...

J

Jacob Wright•1/17/25, 12:21 AM

Yeah, my Cloudflare buildout isn't live. The live product is on Google's Firestore, but DOs will be a lot better. A rate limiter is smart. That will definitely help.

I know DO SQLite is in beta. Has this issue been considered by the DO team? Or is it really a non-issue because of how cheap mostly-empty SQLite files would be?

1

1984 Ford Laser•1/17/25, 12:23 AM

Personally I am still using the KV backend as I have zero experience with SQL and much prefer a document based storage system, which I can mostly replicate with KV. At some point I will move to SQL as it seems to be considerably cheaper, and will be able to handle more complex data setups/relationships. I am using WebSockets, with frequent writes to storage, so SQL makes much more sense
My understanding is that its a non-issue, for that reason and probably others. Any decently large commercial product would have some sort of anti abuse system in place, what that looks like would be entirely dependant on your needs and capabilities. People in here can always provide their input, its interesting seeing how others put things together

Y

yash-notion•1/17/25, 12:40 AM

I'm working on a very simple test on my worker. (i'll link the code below). What i'm confused about, is what should the URL be for the worker in my test? It's example.com in the docs and that doesn't work, I tried using the actual domains i'm deploying on as well as localhost and none worked

import { describe, it, beforeAll, afterAll, expect } from "@jest/globals"
import { unstable_dev } from "wrangler"
import type { UnstableDevWorker } from "wrangler"

describe("Worker", () => {
    let worker: UnstableDevWorker

    beforeAll(async () => {
        worker = await unstable_dev("src/worker/index.ts", {
            experimental: { disableExperimentalWarning: true },
        })
    })

    afterAll(async () => {
        await worker.stop()
    })

    it("should deny request for invalid paths", async () => {
        const cases = {
            failures: ["/", "/foo", "/foo/", "/%2F"],
        }
        for (const path of cases.failures) {
            const resp = await worker.fetch(`http://localhost:3000${path}`)
            console.log(resp)
            expect(resp.status).toBe(404)
        }
    })
})

import { describe, it, beforeAll, afterAll, expect } from "@jest/globals"
import { unstable_dev } from "wrangler"
import type { UnstableDevWorker } from "wrangler"

describe("Worker", () => {
    let worker: UnstableDevWorker

    beforeAll(async () => {
        worker = await unstable_dev("src/worker/index.ts", {
            experimental: { disableExperimentalWarning: true },
        })
    })

    afterAll(async () => {
        await worker.stop()
    })

    it("should deny request for invalid paths", async () => {
        const cases = {
            failures: ["/", "/foo", "/foo/", "/%2F"],
        }
        for (const path of cases.failures) {
            const resp = await worker.fetch(`http://localhost:3000${path}`)
            console.log(resp)
            expect(resp.status).toBe(404)
        }
    })
})

import { describe, it, beforeAll, afterAll, expect } from "@jest/globals"
import { unstable_dev } from "wrangler"
import type { UnstableDevWorker } from "wrangler"

describe("Worker", () => {
    let worker: UnstableDevWorker

    beforeAll(async () => {
        worker = await unstable_dev("src/worker/index.ts", {
            experimental: { disableExperimentalWarning: true },
        })
    })

    afterAll(async () => {
        await worker.stop()
    })

    it("should deny request for invalid paths", async () => {
        const cases = {
            failures: ["/", "/foo", "/foo/", "/%2F"],
        }
        for (const path of cases.failures) {
            const resp = await worker.fetch(`http://localhost:3000${path}`)
            console.log(resp)
            expect(resp.status).toBe(404)
        }
    })
})

import { describe, it, beforeAll, afterAll, expect } from "@jest/globals"
import { unstable_dev } from "wrangler"
import type { UnstableDevWorker } from "wrangler"

describe("Worker", () => {
    let worker: UnstableDevWorker

    beforeAll(async () => {
        worker = await unstable_dev("src/worker/index.ts", {
            experimental: { disableExperimentalWarning: true },
        })
    })

    afterAll(async () => {
        await worker.stop()
    })

    it("should deny request for invalid paths", async () => {
        const cases = {
            failures: ["/", "/foo", "/foo/", "/%2F"],
        }
        for (const path of cases.failures) {
            const resp = await worker.fetch(`http://localhost:3000${path}`)
            console.log(resp)
            expect(resp.status).toBe(404)
        }
    })
})

Similar Threads

Similar Threads

Similar Threads