Let's imagine a real case where 1 million users would connect to and send only 1 message to test the chat room on a monthly basis.
Azure Functions cost : 0$ because the first million is free. Even if they send 10 messages, it's still cheap (2$ as you said)
Now, SignalR :
The free tier does not apply because it allows only 20 simultaneous connections
Standard tier starts at 41,30 € (max 1 million messages, max 1000 simultaneous connections per unit) (let's say 40$)
If we sum up, for a chat room like this (which is very well done and neat, Azure is great, no doubt on that) we have 42$/month.
And as for the 1000 users/day, that's only within the limit of approx 32 messages/user/day on a monthly basis. Pass that limit and you'll need two SignalR units, doubling the price.
Moreover:
If you have more than 1000 simultaneous users, how do you plug new ones to another unit ? This would double the messages sent ?
hi Xavier. I believe Anthony's first response is accurate. We are working on revamping the page for doing calculations on Cloud costs. Hopefully, this will become easier to use quite soon
So we have 60$/month on a 1000 users/day average on a monthly basis, based on Anthony's statement.
Please keep me and readers an posterity informed:
when the Azure pricing calculator will be "revamped" and will accurately evaluate costs (I can't believe the M of GAFAM shouldn't get this fixed within a couple days)
when you will be able to give a clear answer to the costs involved, as precise as the shiny tech bits delivered.
And one last question: Is really al this about technology or is it marketing ? If so, I promess I won't ask anything anymore.
wow, appreciate you replying 2 years after the comment :)
If you have more than 1000 simultaneous users, how do you plug new ones to another unit ? This would double the messages sent ?
mainly around that. We currently have a bunch of signalr pods on a single node, with a redis backplane on that same node, doing around 1 billion messages a month - imagine it's a stock trading app with price updates - but we're at a loss for scaling this out without a backplane, especially signalr onto other nodes. Have you solved an issue similar to ours? I would absolutely love just plugging into an azure service and making that headache an MS problem :P but it seems we're going to have to deal with this one on our own.
I was notified ;) I'm not the author, and no author replied to my questions neither. Seems that your problem is quite different : I was originally stating that omitting the real cost from the discussion was a bit unfair to the audience (ie marketing-like sponsored posts).
You seem to have the $$ so you may get an answer :)
That is the peculiar thing lol, we do, and we really don't want to deal with this problem - but I think it's inevitable :) and I wholeheartedly agree, the marketing-like posts are all fun and jazzy but conveniently step over a lot of the pitfalls of this stuff, especially cost. MS page advises how to scale out with redis, cautions against it (in our case) but never really offers a good alternative.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I did the maths to check, I may be wrong, please correct me if so.
I have used the Azure Pricing calculator.(azure.microsoft.com/en-us/pricing/...)
Let's imagine a real case where 1 million users would connect to and send only 1 message to test the chat room on a monthly basis.
Now, SignalR :
If we sum up, for a chat room like this (which is very well done and neat, Azure is great, no doubt on that) we have 42$/month.
And as for the 1000 users/day, that's only within the limit of approx 32 messages/user/day on a monthly basis. Pass that limit and you'll need two SignalR units, doubling the price.
Moreover:
If you have more than 1000 simultaneous users, how do you plug new ones to another unit ? This would double the messages sent ?
Am I wrong ?
Hi Xavier. I've sent your question to the product team. Hope to get back to you soon :)
Hi Chris, so how did it go with the product team ?
hi Xavier. I believe Anthony's first response is accurate. We are working on revamping the page for doing calculations on Cloud costs. Hopefully, this will become easier to use quite soon
So we have 60$/month on a 1000 users/day average on a monthly basis, based on Anthony's statement.
Please keep me and readers an posterity informed:
And one last question: Is really al this about technology or is it marketing ? If so, I promess I won't ask anything anymore.
Really wish Chris finished off the thread - dealing with similar issues with signalr at the moment.
Cost issues ?
wow, appreciate you replying 2 years after the comment :)
mainly around that. We currently have a bunch of signalr pods on a single node, with a redis backplane on that same node, doing around 1 billion messages a month - imagine it's a stock trading app with price updates - but we're at a loss for scaling this out without a backplane, especially signalr onto other nodes. Have you solved an issue similar to ours? I would absolutely love just plugging into an azure service and making that headache an MS problem :P but it seems we're going to have to deal with this one on our own.
I was notified ;) I'm not the author, and no author replied to my questions neither. Seems that your problem is quite different : I was originally stating that omitting the real cost from the discussion was a bit unfair to the audience (ie marketing-like sponsored posts).
You seem to have the $$ so you may get an answer :)
That is the peculiar thing lol, we do, and we really don't want to deal with this problem - but I think it's inevitable :) and I wholeheartedly agree, the marketing-like posts are all fun and jazzy but conveniently step over a lot of the pitfalls of this stuff, especially cost. MS page advises how to scale out with redis, cautions against it (in our case) but never really offers a good alternative.