First, let me say, I have never worked with Tigase, but nonetheless, here are my thoughts:
I’ve found this on the web:
- prosody setup time: 15mins. ubuntu package, dead simple configuartion, start, done.
- ejabberd setup time: 30mins. ubuntu package, rather simple configuration but need to understand those parameters first related to the erlang vm, start, done.
- tigase setup time: 2h+. tigase tar ball, opendjdk (ubuntu), requires tweaks to resolve issues with jdk tls issues and decouple from databases, a configuration nightmare with endless google searches for documentation until it starts w/o stacktrace.
Openfire is simple to setup in most cases and good to admin (I don’t know how Tigase can be administered).
Openfire has a Hazelcast plugin, which allows you to cluster it. It’s relatively easy to use, but I can’t tell you how good it is in a real world scenario.
Memory and resources:
We had some issues with “non-paged memory” on Windows 2008 with Openfire, which made us move to Linux. No problems so far. (more likely a Windows/driver problem).
I’d say Openfire has 2-3 active developers. I’ve fixed some minor bugs myself. But for me it seems that the core developers from the mid 2000’s, who have the most knowledge about the sources, are gone.
I don’t know about Tigase, but it seems more actively developed. Openfire still has open bugs or feature requests, which are unresolved since 2005, like OF-176
Tigase seems also to support more XEPs (like 0198 Stream Management, or 0079 AMP, or Roster Versioning).
Openfire: Apache 2
Tigase: GPL 3
You can develop/use plugins for Openfire, which is nice. I don’t know how it is with Tigase.