[DO] Clarifying how Durable Object is billed #19752
Conversation
Oxyjun
requested review from
a team,
GregBrimble,
ToriLindsay,
WalshyDev,
irvinebroque and
mikenomitch
as code owners
Oxyjun
changed the title
Oxyjun
added
the
product:durable-objects
github-actions
bot
assigned
GregBrimble,
irvinebroque,
mikenomitch,
ToriLindsay and
WalshyDev
github-actions
bot
added
size/s
and removed
product:durable-objects
Deploying cloudflare-docs with
|
| Latest commit: |
1d63a80
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1fefaf17.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://jun-do-active-time-billing.cloudflare-docs-7ou.pages.dev |
| import { Markdown, GlossaryTooltip } from "~/components"; | ||
|
|
||
| [Durable Objects](/durable-objects/) are only available on the [Workers Paid plan](/workers/platform/pricing/#workers). | ||
| [Durable Objects](/durable-objects/) are only available on the [Workers Paid plan](/workers/platform/pricing/#workers), and are billed while the Durable Object is active (including the <GlossaryTooltip term="event context"> event context</GlossaryTooltip>). |
There was a problem hiding this comment.
Not a blocker for this PR, but I'm curious if "event context" is what we want to use. Request context might make more sense. I have used invocation rather than event elsewhere in the docs. CC: @vy-ton
There was a problem hiding this comment.
Apologies @Oxyjun for getting to this post-merge
I also find request context more clear.
Should we also include The event context for a Durable Objects extends at least 60 seconds after the last client disconnects. mentioned here somewhere on this page below? Otherwise a user could still interpret the removed "Once your Object finishes responding to all requests, it will stop incurring duration charges" to be true.
There was a problem hiding this comment.
Thanks - actioning the points here: #19831
9 participants
Summary
This PR clarifies that DO is billed as long as the DO is active, rather than the active time of a request.
Screenshots (optional)
Documentation checklist