Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Durable Objects in Production

linc.sh

Post reply on HN
Print view View original

11–20 of 58 posts

Re: Durable Objects in Production

#11

Post by throwaway894345 »

minxomat wrote: post #8

I've reached out via the Beta form because I'm so damn excited for that. I have longed tried to map a project of mine (serverless game server for TGC based on workers) onto the available storage tech (KV), but consistency guarantees just weren't where I needed them to be. Hope they'll find a slot soon. Edit: (If someone from CF has questions, you can reach me at hn@elasticwaffle.com) My use case is pretty much exactl…

I’d love to hear more about your use case and the consistency limitations you’re running into!

Re: Durable Objects in Production

#12

Post by minxomat »

throwaway894345 wrote: post #11
minxomat wrote: post #8

I've reached out via the Beta form because I'm so damn excited for that. I have longed tried to map a project of mine (serverless game server for TGC based on workers) onto the available storage tech (KV), but consistency guarantees just weren't where I needed them to be. Hope they'll find a slot soon. Edit: (If someone from CF has questions, you can reach me at hn@elasticwaffle.com) My use case is pretty much exactl…

I’d love to hear more about your use case and the consistency limitations you’re running into!

Feel free to reach out (email in parent post).

Re: Durable Objects in Production

#15

Post by DylanSp »

sfeng wrote: post #9
eli wrote: post #7

Earlier quoted context omitted.

It does support other language, kinda. https://github.com/cloudflare/python-worker-hello-world It just compiles to javascript

Workers actually can run WebAssembly [1], so any language which can target WASM works. I think the rust toolchain is best supported, but there's a fun example with Haskell [2]. [1] - https://blog.cloudflare.com/webassembly-on-cloudflare-worker... [2] - https://blog.cloudflare.com/cloudflare-worker-with-webassemb...

I tried getting Workers to work with a Haskell Servant application compiled with Asterius, based on [1], but kept running into various errors. [2] Example of the perils of trying to use experimental toolchains, I guess.

[1] https://www.tweag.io/blog/2020-10-09-asterius-cloudflare-wor...

[2] For the curious: the problem that eventually defeated me was the Worker responding with 404 to a route on /ip, defined in Servant. I tried defining a route on / with Servant and using that instead, but got 406 responses when doing that. First time I've ever seen that error code.

Re: Durable Objects in Production

#16

Post by sfeng »

DylanSp wrote: post #15
sfeng wrote: post #9

Earlier quoted context omitted.

Workers actually can run WebAssembly [1], so any language which can target WASM works. I think the rust toolchain is best supported, but there's a fun example with Haskell [2]. [1] - https://blog.cloudflare.com/webassembly-on-cloudflare-worker... [2] - https://blog.cloudflare.com/cloudflare-worker-with-webassemb...

I tried getting Workers to work with a Haskell Servant application compiled with Asterius, based on [1], but kept running into various errors. [2] Example of the perils of trying to use experimental toolchains, I guess. [1] https://www.tweag.io/blog/2020-10-09-asterius-cloudflare-wor... [2] For the curious: the problem that eventually defeated me was the Worker responding with 404 to a route on /ip, defined in Servan…

[2] Should be fairly easy to debug, as you can see what routes have actually been bound in the Cloudflare dashboard.

Re: Durable Objects in Production

#17

Post by kentonv »

geelen wrote: post #10
minxomat wrote: post #8

I've reached out via the Beta form because I'm so damn excited for that. I have longed tried to map a project of mine (serverless game server for TGC based on workers) onto the available storage tech (KV), but consistency guarantees just weren't where I needed them to be. Hope they'll find a slot soon. Edit: (If someone from CF has questions, you can reach me at hn@elasticwaffle.com) My use case is pretty much exactl…

Beta invites are definitely flowing now, but I'd recommend pinging someone on Twitter or elsewhere with a quick description of what you're going to build. I think they had so many signups they're worried about opening the floodgates, but on a case-by-case basis there's plenty of room. Maybe?

We really do prefer people fill out the form rather than try to ping us on Twitter. :) https://www.cloudflare.com/cloudflare-workers-durable-object...

We are taking things slowly. Storing data is a big responsibility. We'll need to test with a small number of users for an extended period (a few months) to work out any reliability issues before we really scale up.

Re: Durable Objects in Production

#18

Post by AnthOlei »

I read your write up, but I’m not entirely clear on one part: how do cloudflare workers handle websocket connections? Are they automatically terminated after the worker spends too much time active? If so, doesn’t handling the WS handshake have a lot more overhead than a fetch call? Maybe I’m misunderstanding something here. One of my biggest issues with serverless is its inability to handle websockets in a sane way, so this would be huge.

Re: Durable Objects in Production

#19

Post by DylanSp »

sfeng wrote: post #16
DylanSp wrote: post #15

Earlier quoted context omitted.

I tried getting Workers to work with a Haskell Servant application compiled with Asterius, based on [1], but kept running into various errors. [2] Example of the perils of trying to use experimental toolchains, I guess. [1] https://www.tweag.io/blog/2020-10-09-asterius-cloudflare-wor... [2] For the curious: the problem that eventually defeated me was the Worker responding with 404 to a route on /ip, defined in Servan…

[2] Should be fairly easy to debug, as you can see what routes have actually been bound in the Cloudflare dashboard.

Are you referring to the routes set in wrangler.toml? I tried defining the /ip route there, still got 404.

Re: Durable Objects in Production

#20

Post by haneefmubarak »

minxomat wrote: post #12
throwaway894345 wrote: post #11

Earlier quoted context omitted.

I’d love to hear more about your use case and the consistency limitations you’re running into!

Feel free to reach out (email in parent post).

I'm on the Cloudflare Workers team and while I can't help you get access any quicker than the usual route through the form, I'd still love to hear about your specific usecase(s) and limitations. Is it okay if I email you?
Post reply on HN