Haproxy: Difference between revisions
(Created page with "[https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts Intro]") |
No edit summary |
||
| Line 1: | Line 1: | ||
[https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts Intro] | [https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts Intro] | ||
Two database design choices: | |||
* Each server gets its own quotes and saves all its own data | |||
** Need to read user id from each request and send each user to a predetermined server | |||
** Need multiple Etrade accounts, one for each server, unless we get a deal with Etrade | |||
* Switch to a distributed database with master-master replication | |||
** A lot of work | |||
** Might kill sub-second performance? Might not. We already have delayed-write. | |||
Revision as of 14:17, 9 May 2017
Two database design choices:
- Each server gets its own quotes and saves all its own data
- Need to read user id from each request and send each user to a predetermined server
- Need multiple Etrade accounts, one for each server, unless we get a deal with Etrade
- Switch to a distributed database with master-master replication
- A lot of work
- Might kill sub-second performance? Might not. We already have delayed-write.