|
|
| Line 3: |
Line 3: |
| [https://www.digitalocean.com/community/tutorials/how-to-implement-ssl-termination-with-haproxy-on-ubuntu-14-04 SSL] | | [https://www.digitalocean.com/community/tutorials/how-to-implement-ssl-termination-with-haproxy-on-ubuntu-14-04 SSL] |
|
| |
|
| Two database design choices:
| | [https://cipherli.st/ Cipher configuration] for [https://www.ssllabs.com/ssltest ssl labs] A rating |
| * 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).
| |
Revision as of 23:54, 9 May 2017