[erlang-questions] eJabberd Loadbalancing

[Danil Zagoskin]

Hi!

If you control the client's code, you may make use of XMPP see-other-host
error:
http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions-see-other-host

With it you may make a server which would redirect connecting clients to
the proper server (if needed) just after client tells its JID.



On Mon, Jul 13, 2015 at 9:29 PM, Kannan <vasdeveloper@REDACTED> wrote:

> Hi Team,
>
> We are working on a startup idea that uses eJabberd. We are trying to
> build the load balancing into the client, using a discovery call just
> before the login procedure. There will be a discovery assist node at the
> backend, which maps a chat user to a specific IP. This is some thing
> equivalent to DNS SRV lookup, but more at the application layer, and
> database shards are handled by the application itself. We are of course
> customizing the eJabberd to suit our needs.
>
> Application is handling the sharding, but will get the help of Mnesia for
> replication.
>
>
> Do you see any pitfalls in this method of loadbalancing.
>
> Regards,
> Theepan
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>


-- 
Danil Zagoskin | z@REDACTED
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150730/bd7532c6/attachment.htm>