How does Websocket pricing without Durable Objects work?
If I am using Workers Websocket without Durable Objects (for example using it for listening to queues or as a proxy for another websocket server), how would the pricing work? Is it charged based on per request (hence per websocket connection) and the cpu-time used to process the websocket messages?
1 Reply
That's exactly the question I want to ask 😄