Client load balancing #652
Labels
enhancement
New feature or request
nice-to-have
Desirable for a particular milestone, but won't block milestone release
Milestone
This is one of the new issues that came out of the Friday Engineering call. I think there were a couple of different thoughts around what we were or weren't talking about load balancing. I got the impression that we were talking about putting a load balancer in front of the public-facing RPCs for the protocol, so that any node can go down and we'll still be able to service incoming wallet/client requests.
If this is something different, we should change this description.
I've marked this as nice-to-have because betanet is a really controlled environment with a really controlled set of users and we may be able to do without. That said, it could also be as simple as @mikehostetler or @mattgeddes clicking a couple of buttons in the Digital Ocean UI to have them deploy one for for us as a virtual appliance.
Automating the deployment and configuration of HA Proxy ought to be fairly straightforward as an approach too.
The text was updated successfully, but these errors were encountered: