Hi Mark, an obvious advantage of having a load balancer in front of your Riak cluster is that you will not need to expose your individual Riak nodes directly to the clients. Also, a load balancer will save you from a Single Point of Failure (in case the clients are aware of a single Riak node) or from the need to implement some round-robin or retry strategy in the clients themselves (should the clients be aware of multiple nodes). In a Riak cluster, nodes can disappear and come back. You could instruct your load balancer to automatically remove Riak nodes which are not responding to its pings. Finally, consider that - under certain scenarios - being a coordinator still requires a decent amount of work to do. As an example, during a map-reduce job a coordinator might be responsible not only for routing requests to other nodes, but also for aggregating partial results and for eventually running a reduce phase over the results.
Hope this helps. Roberto Aloi @robertoaloi On Sun, Feb 2, 2014 at 5:18 PM, markrthomas <[email protected]> wrote: > Hello > > Any node in a Riak cluster can coordinate requests for any other Riak node > that is responsible for the data you're reading/writing. > > What is the advantage of fronting a Riak cluster with a load-balancer? > > Thanks > > Mark > > > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/Load-balancer-tp4030414.html > Sent from the Riak Users mailing list archive at Nabble.com. > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > -- Roberto Aloi --- Website: http://roberto-aloi.com Twitter: @robertoaloi
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
