I'm also pretty sure DOs can be cheaper if you are doing CPU intensive workloads
I'm also pretty sure DOs can be cheaper if you are doing CPU intensive workloads
1Yeah Im pretty sure it costs ~$1.70 to run a Worker for an entire day (in pure CPU time only) whereas a DO is like ~$0.34 per day
1Are Durable Object outgoing websocket connections part of the 6 concurrent outgoing connection limit of the runtime?
GDurable Objects are stateful so while active they have to have everything running in reserved memory and storage, and they have a reasonable expectation to be accessible in that time (they could still disconnect or be evicted for other reasons). A worker is ethereal and there is never any requirement or expectation that you are served by the same worker. So it makes sense that workers are billed only for what you use since the server can kill your worker anytime it isn't processing requests and another one anywhere in the network can take that request in its place
GLike the others said, idle isn't counted towards this, and you can have workers handle things on behalf of the durable object if your worried about the time the request would be running
ZGitHub
Summary Add hibernation support for outgoing WebSocket connections created by Durable Objects using new WebSocket(). Currently, hibernation only works for incoming WebSocket connections accepted vi...
TIs there some known issues regarding durable object metrics / observability? When I navigate to durable objects in console, already in the listing I see error rates that make no sense. Selecting one of the durable object with seemingly high error rates I see a diagram like this.
Searcing the logs I find no errors or exceptions, and this 96% error rate does not correspond at all to what is happening in reality with the durable object.
Searcing the logs I find no errors or exceptions, and this 96% error rate does not correspond at all to what is happening in reality with the durable object.
BNot seeing the same
L- What are the costs of calling `storage.deleteAll()` ?Let's say I have 1M rows in a table, will I be billed for 1M rows written as all 1M rows must be deleted?
- Are there any plans for read replicas for DOs?
LAre there any plans for read replicas for DOs?Yes, once D1 read replication is Generally Available, we will open up replicas for DOs too (or around that time), since the underlying infrastructure is the same. D1 read replication uses DO read replicas.
BThat's exciting.
JAny chance we'll be seeing it this week? 
BSo.... it's ready, but... 
just finishing an internal audit before we release
just finishing an internal audit before we releaseJVery exciting! I assume you can't really say how long those usually take haha?
JIt's not like it's urgent to me, but it's still very exciting to see - coz it's long overdue
Bam I allowed to say "this week" again?
J
PI am in a hard release too, can't blame you Brayden ! Be proud it's a game changer feature.
LBrayden didn't learn yet not to give out ETAs If there isn't an ETA, you cannot miss it.
If there isn't an ETA, you cannot miss it.
LI know how deletes are billed. What I don't know is if calling which effectively removes DO is treated the same or not.
Gdoes anyone know how to override the RPC Timeout? We're streaming data using ReadableStream over RPC, but the 100s time limit is too low for long-running AI responses. is defined here: https://developers.cloudflare.com/api/resources/zones/subresources/settings/models/proxy_read_timeout/
Interact with Cloudflare's products and services via the Cloudflare API
MIs it possible to view an account wide “Service Map” or “Topology View” showing all Workers, Durable Objects, and their bindings/dependencies in the dashboard?
Currently, each individual Worker page in the dashboard displays its bindings and dependencies (Durable Objects, KV, R2, etc.), which is helpful, but there’s no system-wide view that connects them all.
Currently, each individual Worker page in the dashboard displays its bindings and dependencies (Durable Objects, KV, R2, etc.), which is helpful, but there’s no system-wide view that connects them all.
LI don't think this exists right now, although it's been discussed a couple of times.
MWith many Worker and Durable Object classes, it’s challenging to get a high-level picture of how everything fits together.
LThe UI gets a lot of love lately, so I am sure (or I hope) this will get some attention at some point as well.
NIs there any way to access the request ID of the worker that called the durable object from inside the handler somehow? Without having to manually plumb it in.
LAre you using RPC for the call?
LWhere is the request ID coming from in the Worker? Headers on an HTTP Request?
II am trying to create a worker with a durable object attached via Terraform. However, I keep on getting “Cannot create binding for class 'Aggregator' that is not exported by the script.” However, I do export it:
Is there something that is typically missed?
Is there something that is typically missed?
Nyes using RPC for the call. The requestID is the one that we get from the cloudflare header, which also ends up in the observability logs somehow
IJust maybe putting Terraform aside for a second, when I go via the UI and try to bind, it does not seem to see any durable objects exported in the script. I guess there is some misunderstanding from my side. What is going on here? How does one create durable objects?
1Have you added the binding to wrangler config?
MYou'll want to ensure that the Durable Object class is exported in your main workerfile
You also need to configure the
You also need to configure the
wranglerI have a question about durable object pricing with RpcTarget. If my durable object has returned an RpcTarget (allowing me to amortize multiple calls within the same RPC session) am I correct to assume that while the RpcTarget stub is alive (hasn't been disposed of), the durable object must be actively running and billing me? I have a worker that makes multiple calls to a durable object, but between each call there's slow calls to an external service. If the durable object will be billing me for the whole rpc session, my guess is it would be cheaper to break into multiple shorter rpc sessions. Appreciate any clarifications!
Awhat can be done to prevent a malicious actor from sending too many websocket messages to a durableobject? there seems to be some internal queue of incoming messages that's getting flooded (even before the requests reach my DO's code)
MYou could try the Firewall API and create a new rule, https://developers.cloudflare.com/api/resources/firewall/subresources/rules/methods/create/
Interact with Cloudflare's products and services via the Cloudflare API
MWhat malicious actor is causing the problem @Avi?
Athis is apparently deprecated? to be clear the issue is the frequency of sending of traffic. i'm looking for a ratelimit, not to block a particular actor indefiniteyl
Ait's a videogame, so people who are looking to cheat
MThanks. Yes. The new API appears to be: https://developers.cloudflare.com/ruleset-engine/rulesets-api/create/
We are using the legacy API in production at the moment. Idea is to make API call to CF to dynamicaly manage firewall rules to prevent connection from happening in the first place.
We are using the legacy API in production at the moment. Idea is to make API call to CF to dynamicaly manage firewall rules to prevent connection from happening in the first place.
Aright, i wouldn't want to prevent the connection entirely
Ajust to say, limit the number of messages being sent to X per Y amount of time
MRateLimit?
Ayes
MThere is a new built-in rate limiter here: https://developers.cloudflare.com/workers/runtime-apis/bindings/rate-limit/
We have custom RateLimit durable object here which has configurable locking settings
We have custom RateLimit durable object here which has configurable locking settings
Aooo that's cool, hadn't seen this before. although i doubt it would work for websocket messages
Myou can make a new DurableObject instance that acts a rate limiter, its very easy
Mand use custom business logic from your app
Ai don't follow. you're saying create a second DurableObject?