[
https://issues.apache.org/jira/browse/SYNAPSE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton resolved SYNAPSE-360.
----------------------------------
Resolution: Fixed
Fix Version/s: NIGHTLY
Fixed on the SVN trunk.
> Dynamic load balancing
> ----------------------
>
> Key: SYNAPSE-360
> URL: https://issues.apache.org/jira/browse/SYNAPSE-360
> Project: Synapse
> Issue Type: New Feature
> Components: Endpoints
> Affects Versions: NIGHTLY
> Reporter: Afkham Azeez
> Assignee: Ruwan Linton
> Fix For: NIGHTLY
>
> Attachments: dynamic-lb.patch
>
>
> There are some limitations in the current load balancer implementation. e.g.
> if we have 2 identical services in 2 different worker nodes, which are
> fronted by a synapse load balancer instance. In such a case, we need to
> provide 4 endpoints in the synapse.xml file. As can be seen, this is not a
> very scalable solution. Hence, I have implemented an dynamic load balancing
> mechanism where the application members are discovered at runtime, and the
> endpoint do not need to be statically specified in the synapse.xml file.
> Currently, the application endpoints are calculated by replacing the IP and
> port of the incoming request with that of the member to which this request
> will be forwarded to. I have only tested with HTTP/S for the moment. More
> details about the concept & design can be found here:
> http://afkham.org/2008/06/fault-resilient-dynamic-load-balancing.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
