←back to thread

285 points ajhit406 | 6 comments | | HN request time: 0.62s | source | bottom
1. braden-lk ◴[] No.41833493[source]
Durable objects seem so cool but the pricing always scares me. (Specifically, having to worry about getting hibernation right.) They’d be a great fit for our yjs document based strategy, but while everything in prod still works on plain ol redis and Postgres, it’s hard to justify an exploration.
replies(3): >>41833710 #>>41833761 #>>41835916 #
2. ignoramous ◴[] No.41833710[source]
> Specifically, having to worry about getting hibernation right.

As long as the client doesn't exchange websocket messages with DO, it'll hibernate. From what I can tell, ping/pong frames don't count towards uptime, if you're worried about that.

3. attilakun ◴[] No.41833761[source]
Does CloudFlare have proper spending caps? If they have, I'd be open to try DOs but if they don't, it's a non-starter for an indie dev as I can't risk bankruptcy due to a bad for loop.
replies(1): >>41834546 #
4. viraptor ◴[] No.41834546[source]
It's not just the listed prices either. There was a story here not long ago where they essentially requested someone to migrate to an enterprise plan or get out. With AWS it's pretty common to get a refund for accidental abuse. From my contact so far and from stories here, I wouldn't expect anything close to that treatment from CF.
5. anentropic ◴[] No.41835916[source]
What scares me is it is super specific to Cloudflare

What is your option if you want to eject to another cloud?

replies(1): >>41839677 #
6. paulgb ◴[] No.41839677[source]
For the specific example of a Yjs backend, I happen to be working on one that can be hosted either on Cloudflare or as a native process. We’ve had people running in production migrate from cloudflare to native just by swapping out the URL they connect to in their application config.

https://github.com/jamsocket/y-sweet