Ejabberd is a good option.
Ask HN: XMPP/Jabber self hosting
11–20 of 48 posts
Re: Ask HN: XMPP/Jabber self hosting
#12I've run ejabberd and openfire. I had issues with ejabberd and load issues. I use openfire now. XMPP is kind of beast. With ejabberd and openfire had to get into the code and debug it myself. If I stick with XMPP I'm can see myself wading hip deep in the code.
I'll have to take a look at prosody.
Re: Ask HN: XMPP/Jabber self hosting
#13I'have been using Tigase for our chat application (https://play.google.com/store/apps/details?id=com.hyperon.sm...) the decision of selecting server depends totally upon your requirement. I have used Tigase, Openfire and Jabbered 2 for different projects and have done with lots of customization in them.
If sclability is your main requirement my suggestion would be
1- Tigase 2- Jabbered 2 3- Openfire
I have also heard of Ejabbered a lot but that is in erlang ( which i don't like ) My top priority is always Tigase ( the only bad thing about it is you really need to dig into it to manage because there isn't lots of support available in term of blogs tutorials etc) Hope it will help you in choosing your preferred one ....
Re: Ask HN: XMPP/Jabber self hosting
#14Re: Ask HN: XMPP/Jabber self hosting
#15I've set up a XMPP server using Prosody after evaluating what are typically regarded as the top 3 implementations (ejabberd, Openfire, and Prosody).
I ended up with a Prosody install primarily for two reasons: 1) Memory consumption/stability 2) Authentication support
The XMPP server hosts up to 700-800 simultaneous users and is located on a machine that provides many other services. With both ejabberd and openfire at this scale, memory consumption was in the several hundred megabyte range and (specifically ejabberd) typically had CPU load of 10-20% of a core.
The prosody setup I ended up using was significantly more lightweight and was simple to set up with server authenticating logins against TLS-enabled LDAP.
In the past, ejabberd was avoided because of serious security issues with the software, but in the past few years it looks like they've gotten their act together somewhat. That said, there's still some recent CVEs, you would want to pay attention to this if deploying ejabberd in any public-facinc infrastructure. As an example, ejabberd used to _require_ storing all passwords in plaintext, claiming that this was "more secure" than the alternatives (ref: https://www.ejabberd.im/plaintext-passwords-db)
Re: Ask HN: XMPP/Jabber self hosting
#16I'have been using Tigase for our chat application ( https://play.google.com/store/apps/details?id=com.hyperon.sm... ) the decision of selecting server depends totally upon your requirement. I have used Tigase, Openfire and Jabbered 2 for different projects and have done with lots of customization in them. If sclability is your main requirement my suggestion would be 1- Tigase 2- Jabbered 2 3- Openfire I have also hea…
http://stackoverflow.com/questions/8670234/scaling-tigase-xm... is a good link if you want to know why i prefer Tigase ....
Re: Ask HN: XMPP/Jabber self hosting
#17ejabberd is written in Erlang which was a turn off for me. Maybe not for you.
Re: Ask HN: XMPP/Jabber self hosting
#18I've been though jabberd2, ejabberd and has since a couple of years stuck with Prosody.
The main strengths are that it is very simple and lightweight, and uses less resources. The drawbacks is that it is simple and lightweight, so anything more complicated for corporate deployments is something you often have to roll up your sleeves and implement yourself.
I was scared to run it at first because it is written in Lua, which is an unknown language to me. However, I must say it is quite an elegant language. I could get an authentication plugin running after looking at an existing one, and I trusted it enough to run in production internally for a small team (and it turned out to work well for us).
Edit: Be sure to get a real certificate (startssl is fine), if you intend to use s2s. During the past year or two, most public servers has started to care.
Re: Ask HN: XMPP/Jabber self hosting
#19I run ejabberd on my personal domain. It was easy to set up and has run without really needing any active management for a few years now.
I "third" that.
A nice C++ client library is by the way http://swift.im/swiften/.
Re: Ask HN: XMPP/Jabber self hosting
#20I run ejabberd on my personal domain. It was easy to set up and has run without really needing any active management for a few years now.
I've had similar success, probably over the course of 8 or so years. I've moved it from from machine to machine a few times, and generally haven't had any issues with it. I've had to hack the source once or twice to work around various stupid things on my machine (for instance, my Kerb setup was very slow once, and I had to hack epam not to time out); the source is pretty reasonably maintainable.
I've heard good things about Prosody, but haven't compared the two of them directly.
It is said that ejabberd supports XEP-0136 (server-side message archiving), but since it's not a default (at least, I don't think), I haven't turned it on yet. One of these days I will give that a try.