4 ms·
Yeah, I hear you. Which is why we assessed and designed our own platform for handling the above stated traffic (and much more) for multi-user real-time chat ses
by softfalcon 2y ago
Yeah, I hear you. Which is why we assessed and designed our own platform for handling the above stated traffic (and much more) for multi-user real-time chat sessions.
The commenter seems to know a lot about Jazz, so I took the opportunity to ask further questions.
- theanzelm 2y agoI made Jazz, that's why I know a lot about it ;) (I now have people helping me) Let me know if you'd like to know anything else.
- bilekas 2y agoI like the idea, I have some implementation questions but I’ll catch you on GitHub. Nice work so far though.
- bilekas 2y agoGood stuff, and I hope I didn’t come across too rude but 10k parallel is not a problem for even basic setups to manage, it’s a problem solved many different ways some out of the box some not. Maybe your question was phrased wrong. But hit into 10kk parallel, there’s an interesting metric to discuss optimization. I’m reminded of the quasi meme “You have designed an infinitely scalable service for 10 clients “
- softfalcon 2y ago10k parallel users I agree, but 10k receiving all updates from the other 9999 and vice versa can become quite a complex problem to solve. Especially within time (latency), monetary hosting cost, and accuracy constraints. For example, an MMO town with 10,000 connected clients all viewing the same complex session state of all other users and entities in one town. That’s a lot of room for error. Or am I missing something? That scenario is complex to me and has remained complex to me despite my various times building it out for various products.