This is one of those pieces of software that I've basically never run into issues with. XMPP itself is rather a moving target, so reviewing which modules are enabled from time to time is necessary, but other than that administering it is a breeze.
What people use nowadays as a database with ejabberd? I was a user of a ejabberd service 20+ years ago and mnesia (which at that time was the default option) was the reason for frequent downtimes. As a user I don’t know details but ejabberd+mnesia didn’t look robust.
This is one of those pieces of software that I've basically never run into issues with. XMPP itself is rather a moving target, so reviewing which modules are enabled from time to time is necessary, but other than that administering it is a breeze.
Used to work great even on low specs servers, web UI was horrible. I am willing to install it again. No matrix, no slack, worried about Telegram.
Erlang goodness.
Say what you will about XMPP, but it Just Works, supported by robust software like this.
What people use nowadays as a database with ejabberd? I was a user of a ejabberd service 20+ years ago and mnesia (which at that time was the default option) was the reason for frequent downtimes. As a user I don’t know details but ejabberd+mnesia didn’t look robust.
ejabberd's documentation warns you against using mnesia for chat logs because it apparently has a hard cap on volumetry. Any SQL DB does the job.
Pgsql for me.