Ejabberd vs openfire in terms of user handling

I want to know how many exact concurrent users EJabberd can support . Currently we have openfire as our XMPP server and we are considering to migrate to Ejabberd as in future our number of concurrent users will increase and Ejabbered is more robust in production environment . But one drawback is Ejabberd is written in
Erlang and what if we want to modify as we donot have Erlang expert .
In short we want to make comparison Open fire and Ejabberd in terms of number of concurrent user handling , robustness and ease of configuration and maintenance, extensible and which one is more suitable on production environment

Hello, I cannot tell about

Hello,

I cannot tell about Openfire. All I can say is that we are managing clusters supporting tens of millions users, millions of active users.

ejabberd is extremely robust and massively scalable and is used to power the largest XMPP deployments in the world. You cannot go wrong with ejabberd in term of scalability.

thats good but what if we

thats good but what if we want to customize any module with no expertise in ERlang how hard to learn and get into erlang???????

Erlang is not that hard and

Erlang is not that hard and we are working on improving the developer documentation.

Moreover, ejabberd can now be extending in Elixir language, which is close to Ruby in term of syntax. That should make it even easier to extend ejabberd.

Ok that is good . What about

Ok that is good . What about hosting ejabberd server to windows azure it will be easy to host our chat server (EJabberd) on cloud? as Open Fire using java and I think for java, support is there on windows azure but what about ERLang ?

You can easily host ejabberd

You can easily host ejabberd on Azure, but you will need to use an Azure Linux instance.

Syndicate content