Yes. But every chat application in node.js that has ever been presented in HN faced the same fate of being brought down to a crawling pulp whenever it had more than 100 or so concurrent users.
Which is a bit amusing, as I remember standalone IRC servers handling 40,000+ peak users with relative ease -- and that was back in the late 90s on commodity server hardware.
40k might be pushing it, but 10-15k should be no problem on current hardware.
More importantly IRC servers have a battle hardened scaling solution baked right in, based on the spanning tree protocol.
Anyone looking to write a scalable chat software would be well advised to study the evolution of IRC. Anyone looking to hack a scalable chat solution would be well advised to use a mature IRCd for the backend.
Edit: I hung out on DALnet back when twisted was still linked and when it got taken down the crush of the users, as the article mentions, rendered the network virtuall inaccessible. Goes to show what happens when you rely too much on one link.
This makes me wonder, what is the difference in technologies? I never used IRC to be honest, was it downloadable software or was it web based? (I'm not that young I swear, I'll be 35 next week - I just didn't do chat)
Popular GUI-clients would be Colloquy on Mac, mIRC on windows and XChat on linux. Just download one and see for yourself; Freenode is a popular network for hackers of all kinds, QuakeNet is the network for gamers (and also happens to be the biggest with ~60k users online at any given time).
It's just done well. It has stood the test of time, and seen nearly 30 years of development in multiple, competing irc server products. A lot of rivalry and different views and attitudes to certain strategies.
IRC is amazing. Servers are linked as leaves to hubs, or as hubs, linking to other hubs or leaves. If the network splits (one server goes down, breaking the tree) it can be quickly relinked to secondary or tertiary servers, restoring connectivity. For its time, and even to this day, it is an impressive protocol that is not only fairly easy to implement from a client perspective, but a very scalable chat server architecture.
