BeBoRE
Problem using EventEmitters [Weird behavior]
I use redis for my project https://github.com/bebore/ei-noah-bot but that's quite complex, I recommend just following the redis package docs. It's not much different from the event emitter other than that you need to (de)serialize the input and output.
16 replies
Cloudflare worker subscriptions/websockets
Yeah, not using hibernation could increase costs especially, but at lower scales I wouldn't worry about it. Good thing about the fetch adapter is that you can switch to a different service pretty easily, so you aren't that vendor locked.
7 replies
Cloudflare worker subscriptions/websockets
Pretty sure the fetch api handler works fine
https://trpc.io/docs/server/adapters/fetch
As you stated it doesn’t use durable objects, so that could increase costs.
7 replies
use cases
IMO tRPC is best used in a context where one container needs to communicate to another container where the input cannot be fully trusted. So yes this could be client -> server communication, but I’ve also seen it used in Electron applications where the render thread communicates with the main thread.
24 replies
websocket or sse
Should be the same concept, they also use an EventSource etc.
https://vercel.com/blog/an-introduction-to-streaming-on-the-web
Maybe subscriptions are too long running
15 replies