Websocket Costs estimation - The rabbit hole
I've been deep diving into the CF documentation and blogs for days, trying to crack the code on cost estimation, but I'm still lost in the fog. SOS! HILFE! :NotLikeThis:
I need some help to estimate potential costs for using WebSockets.
Example scenario: Let's say I've got 10 clients (front-ends) connected, and I'm sending 2 basic individual messages to each client every second (10kb pay load each?) = 20 messages/s. = 200kb/s. = 51,840,000 messages /month
I don't use cache, but I might use D1, queues, or other workers to push messages,
so what moneys it could cost me? if I run this WebSocket 24/7?
And would it be cheaper than just making 20 standard worker invocations /second (client<>worker)?
Thanks a million for any insights you can share!
:bibicat:
I need some help to estimate potential costs for using WebSockets.
Example scenario: Let's say I've got 10 clients (front-ends) connected, and I'm sending 2 basic individual messages to each client every second (10kb pay load each?) = 20 messages/s. = 200kb/s. = 51,840,000 messages /month
I don't use cache, but I might use D1, queues, or other workers to push messages,
so what moneys it could cost me? if I run this WebSocket 24/7?
And would it be cheaper than just making 20 standard worker invocations /second (client<>worker)?
Thanks a million for any insights you can share!
:bibicat:
