Hi,
i have a doubt about what configuration to choose between federation and clustering in a particular scenario.
In my scenario, a remote office which has an unstable connection, employees there can authenticate on a local instance of ejabberd, but when the employee travels or work from home, he would like to exchange messages with his collegues at the office. I can install another instance of ejabberd on the cloud, but in this case how this instance can 'sync' with the local office instance?
I wonder what is the suggested configuration for this scenario?
it seems nor federation neighter clustering can solve the different problems:
1. federation: the user can authenticate even remotely, but the local office server should be always reachable (not the case), otherwise the travelling user cannot authenticate.
2. clustering: i am not confidente that a clustering over WAN, is a good practice, then how clustering will behave on an unstable connection, loosing packets time to time.
Somebody faced such problems before? is there a optmal solution in your opinion or a custom development is needed?
thanks in advance,
Regards,
Luke
Hello, Here are my
Hello,
Here are my comments:
1. federation: Each ejabberd cluster / instance will have its own domain but you should be able to make it work like you want.
2. clustering: Erlang clustering in ejabberd is not intended to work over WAN cluster. You need low latency connection and always on link between the nodes, so it will not work in your case.
I hope this helps,
thanks, it helps
thanks, it helps indeed.
about federation, if the two nodes in federation will have different domains, it means the user will have two JID, right? so it will appear as two different users when he is travelling or in office, and two rosters.
it is not an ideal situation.
Well, yes, but if you control
Well, yes, but if you control the backend you could try to trick ejabberd to serve the same contact list, etc.
It depends on what you want to do. For example, if this is mostly groupchat, it may not matter.