| 1 |
Am Freitag, 4. November 2011, 14:22:38 schrieb Alexander Tanyukevich: |
| 2 |
> 2011/11/4 Jorge Martínez López <jorgeml@×××××.com>: |
| 3 |
> > I played some years ago with Openfire: |
| 4 |
> > http://www.igniterealtime.org/projects/openfire/ I did not test the |
| 5 |
> > integration with Asterisk, but it sounds promising. |
| 6 |
> > |
| 7 |
> > Cheers, |
| 8 |
> > |
| 9 |
> > -- |
| 10 |
> > Jorge Martínez López <jorgeml@×××××.com> http://www.jorgeml.net |
| 11 |
> > Google Talk / XMPP: jorgeml@×××××.com |
| 12 |
> |
| 13 |
> I've asked that question on couple of forums and everytime got answer: |
| 14 |
> "ejabberd". But there was no arguments. And actually I've never used |
| 15 |
> it because of erlang :) |
| 16 |
|
| 17 |
ejabberd supports clustering. New servers can be added or removed from the |
| 18 |
cluster without stopping anything. This is also a plus for fault-tolerance. It |
| 19 |
scales to 1.000.000s of users without any problems. erlang is designed for |
| 20 |
problems like this and it's really good in this domain. ejabberd is quite easy |
| 21 |
to extend via hooks. Of course, you need to learn erlang to do this. In the |
| 22 |
simple case, you write some glue code in erlang (typically 20-30 LOC) and do |
| 23 |
the work in the language you are most familiar with. You can even add C- or |
| 24 |
Java-Nodes to your cluster, that can talk to the ejabberd's via erlangs native |
| 25 |
message-passing. |
| 26 |
In the company I worked for, we have an ejabberd-cluster with millions of |
| 27 |
accounts (iirc something like 20 million customers at the time I left) |
| 28 |
We evaluated ejabberd, OpenFire and jabberd, but only ejabberd was able to |
| 29 |
cope with our load. |
| 30 |
|
| 31 |
Best, |
| 32 |
Michael |
Archives