Hacker News new | ask | show | jobs
by jaflo 802 days ago
When I took a look at using DO last time I decided against using them because you had to pay for the duration your clients are connected to them when using WebSockets. As far as I understood it’s not execution duration but flat out how long your clients are connected. You’ll burn through seconds quickly that way. I decided to go with a polling mechanism instead.
1 comments

They have hibernating durable objects now that don’t charge unless there is a request through them: https://developers.cloudflare.com/durable-objects/api/websoc...
Oh that’s neat! I’m not sure if it didn’t exist or if I didn’t find this last time. Looks like this would address the problem.