Haproxy: Difference between revisions
No edit summary |
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] | ||
[https://www.digitalocean.com/community/tutorials/how-to-implement-ssl-termination-with-haproxy-on-ubuntu-14-04 SSL] | |||
Two database design choices: | Two database design choices: | ||
Revision as of 15:02, 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.
For the first 1000 paid users, we will NOT do load balancing.
Instead, we will just use haproxy to redirect (bitpost.com IP) + port 8080 requests to abettertrader.com (all https).