Hi,
I was wondering what would be the best architectural strategy for maintaining Ejabberd infrastructure, wherein some pubsub nodes will have a lot of subscribers while some won't have a lot.
Also, if I am using a ReST API for ejabberd authentication, how would that integrate with a Ejabberd cluster setup?
And, does sharing a common MySQL odbc database/ ReST API among nodes(cluster) defeats the purpose of clustering?
I want to achieve the best possible throughput for the pubsub infrastructure with a ReST API as the backend. So please suggest best practices and/or optimizations in this regard.
Thank you.
