Ejabberd scalability: single node with 2M concurrent users (2016)
process-one.net
process-one.net
I remember Nintendo adopted it for their push platform [1] but it was old news. Are there any interesting development and/or adoption stories in recent years?
[1] https://www.process-one.net/blog/ejabberd-nintendo-switch-np...
The main problems with the earlier versions of ejabberd were:
1. Using Erlang strings (linked lists of UTF32 codepoints) instead of UTF8 binaries, which led to 16x more RAM use.
2. Over-reliance on Mnesia for session management which is a maintenance nightmare when used in large clusters. Now it can be replaced by Redis or your own DB.
3. Non-scalable default implementations for mod_muc (Multi-User Chat) and mod_pubsub.
4. Absence of built-in mobile push support.
That was before WhatsApp, which later committed upstream many of their scalability improvement to the BEAM VM.
Source: I scaled an old ejabberd cluster to 500K concurrent users, and wrote my own Erlang-based Long-Polling/Websocket Pub/Sub servers and MQTT brokers scaling to 1M concurrent connections per node in a cluster. Also Elixir-based specialized messaging systems.
I fully support this sentiment when talking about consumer messaging apps.
I once joined a hackathon where organized asked participants to use 4 different consumer messaging apps, each for a different purpose.
It's a mess, not sure if Google's RCS will solve it. Maybe governments need to force interoperability by law.
What I meant by "custom" is "industry-specific". One of the first B2B uses for Instant Messaging was in Finance/Trading. There are many industry-specific messaging apps, each answering specific needs and/or compliance/regulation issues.
Also in many cases you need a messaging/notification feature for an existing app, and using a full-blown messaging service is an overkill and/or doesn't fit your app.
> Please use standard existing protocols. If XMPP is not your jazz, there are others.
I did lots of XMPP-based projects. I also developed my own MQTT brokers/gateways. I'm following Matrix development.
MQTT is too lightweight for human messaging. Matrix is certainly better than XMPP, but it's not designed to be easily embedded into an existing app. You have to write a bridge which is problematic. Matrix is really a decentralized conversation store rather than a messaging protocol.
... and IRC is too old ;)
This is what the EU is doing, although I fear for E2EE in cross-app scenarios.
The XMPP newsletter[2] is a good summary of what is going on in the world of XMPP.
But there is also an iOS app and a self-hostable server. All these components build on open-source projects (working with and supporting upstream whenever relevant).
Our goal is to have a suite of software across platforms that is a consistent, integrated and family-friendly while being fully open-source and open standards: https://snikket.org/about/goals/
To get back to familiar technical ground, try Synapse. A node can support, like, 3 concurrent users.
I wish you would joking. But it doesn't depend so much on the users but more on the size of the room / amount of events and the amount of other servers in the room.
However Matrix solves a different problem https://github.com/jryans/awesome-matrix#research so it's a bit unfair to compare both.
I hope someday someone pulls off an memory/cpu efficient matrix protocol implementation. https://conduit.rs/ looks good and there is still work on construct the c++ server: https://github.com/jevolk/charybdis - but both only implement a subset of the rather huge and complicated spec at the moment.
I’m sure they have a wealth of knowledge related to scaling since WhatsApp was initially based on ejabberd.
Not only WhatsApp, but also the initial implementation of APNs (Apple Push Notification System) was based on ejabberd. They even used the same port numbers. I did an ejabberd scaling training in SF in 2011, and there were several Apple guys. It doesn't mean that they're used ejabberd for sure, but it's a hint.
Have file transfers over xmpp gotten any better in the last decade?