Pros y Contras de ejabberd

Ejabberd is Erlang OTP application. OTP means open telecom platform. It is highly performant and very mature. It is designed for building distributed concurrent applications. OTP is a set of design patterns and project structure. If you follow OTP principles uses OTP tools for composing components you guaranteed to get robust product. Erlang OTP is what i like the most.

Ejabberd typical setup is working out-of-box. It is efficient. Standard two nodes cluster can handle 1M concurrent users on 300M memory per node. Reseña recopilada por y alojada en G2.com.

It is hard to extend without losing original robust implementation. Even there is plugin architecture.

ejabberd has been started in 2004 by one person. It contains lots of legacy code. Many things could be done more clear way. I think that is the result of learning curve. The software evolved along with the platform. Nokia tried to adopt it in 2009 but failed integrating Single Sign One module. Its server never reached product quality. Finally they used java based implementation for Push messages infrastructure.

I do not like unnecessary generalisation in modules. There is core modules as message router i spent months debugging. Reseña recopilada por y alojada en G2.com.

IOT environment, with various devices, connected to each other and server to do what you want Reseña recopilada por y alojada en G2.com.

communication breakage between devices. Reseña recopilada por y alojada en G2.com.

I was looking to setup a server for a Xmpp chat service. One of the main requirements was that it should be scalable for high throughput communication and this fit the bill perfectly. Reseña recopilada por y alojada en G2.com.

The main source of discomfort was that it was written in erlang, a language I was not comfortable with. Reseña recopilada por y alojada en G2.com.