I'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 ....
Ask HN: XMPP/Jabber self hosting
31–40 of 48 posts
Re: Ask HN: XMPP/Jabber self hosting
#32I'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…
I run it on a much smaller scale with imap authentication and it works flawlessly.
Re: Ask HN: XMPP/Jabber self hosting
#33Re: Ask HN: XMPP/Jabber self hosting
#34https://www.hipchat.com/server is all of the functionality (persistent searchable rooms, image uploads, mobile clients, video, emoticons (allthethings) etc.) of HipChat.com but behind the firewall (on premise). Disclaimer I'm a dev on the project, though to be fair everybody in the Beta has been happy with it.
Re: Ask HN: XMPP/Jabber self hosting
#35https://www.hipchat.com/server is all of the functionality (persistent searchable rooms, image uploads, mobile clients, video, emoticons (allthethings) etc.) of HipChat.com but behind the firewall (on premise). Disclaimer I'm a dev on the project, though to be fair everybody in the Beta has been happy with it.
I never knew hipchat was a jabber system
Re: Ask HN: XMPP/Jabber self hosting
#36https://www.hipchat.com/server is all of the functionality (persistent searchable rooms, image uploads, mobile clients, video, emoticons (allthethings) etc.) of HipChat.com but behind the firewall (on premise). Disclaimer I'm a dev on the project, though to be fair everybody in the Beta has been happy with it.
I never knew hipchat was a jabber system
Re: Ask HN: XMPP/Jabber self hosting
#37Re: Ask HN: XMPP/Jabber self hosting
#38I also had the pleasure working with ProcessOne via the Business edition ejabberd support, as well as commissioning them to build few custom modules that would have taken my C++(embedded team)/C#(back-end team) centric team much more time and money to build ourselves. So ejabberd is a great way to both get your feet wet(open source community version), then scale up in a big way with professional support(commercially licensed business version) should it be needed.
Note: I am not affiliated with ProcessOne in any way. Just had a pleasant experience working with them, and greatly enjoy their product.
Re: Ask HN: XMPP/Jabber self hosting
#39I 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.
That's what I run, too. The only time it died on me is when I updated and they had changed the configuration format to yaml (without an automated conversion). Aside from that annoying hiccup, it's been very smooth sailing. It federates well (though I lost IM access to a lot of friends when Google killed gchat federation). The nice thing about running my own server is that when I talk to other people that have account…
Re: Ask HN: XMPP/Jabber self hosting
#40I've been using Prosody for ~2 years on a couple servers and I can't recommend it highly enough: it's extremely simple, lightweight, and easy to configure. Its author is even on HN. https://prosody.im/ I don't recommend ejabberd, unless perhaps you need to cluster. It consumes a lot of memory, which is undesirable on a VPS, and once I managed to get an ejabberd server into such a weird state that it required dropping…
Source: Last company I worked for used XMPP as the data channel to and form our data center and IoT/SCADA devices, I oversaw the project of upgrading from a much older version of ejabberd (which used erlang strings) and the much newer community edition ejabberd(which uses binary strings).
You can also write a custom module and use ejabberd solely for it's XMPP wire protocol and excellent routing features, but immediately export incoming data from the server to other processes in your stack without ejabberd ever even parsing the incoming XML(in this case we wrote a rabbitMQ ejabberd module which allowed ejabberd to interact with our data center flawlessly), which is what we did and at that point, a single XMPP server was able to handle our entire traffic. Although we obviously used a cluster and HA load balancer for scalability and redundancy.