本文共 1351 字,大约阅读时间需要 4 分钟。
We can use Load Balance strategy to increase the system volume .
Part 1: LB hardware/software horizontal comparison
the following is the cost and capability estimation:
Technology
| Hardware(H)
/Software(S)
| Advantage
| Disadvantage
| Capability
(Support how many concurrent sessions) | Cost
|
F5 BIG-LTM-3400-RS | H | · Fast Speed (millis-second level) · High Availablity(99.9999%)
| · High Cost | >4,000,000 | 370000RMB |
LVS(for Linux) | S | · Best Performance in Software HB solution · Don’t need so many configuration · Hot backup solution | · Don’t support regular expression · Can’t support dynamic-static page separation
| >100,000 | Free |
Nginx | S | · More flexible ,especially support regular expression · Less dependency on network, if pings well ,it can do LB · Easy install and config · Support high concurrency · Good technical community support | · Only support http and email ,it can’t hold session | >10,000 | Free |
HAProxy | S | · Can support http ,tcp ,email · Can hold session
| · Don’t support apache logging format · Need to configure a lot of ACLs | >10,000 | Free |
|
|
|
|
|
|
Part 2: My Suggestion
if budget is enough ,we can use two layers:
Layer 1: use F5 (hardware) to load balance every request
Layer 2: use several Nginx server to load balance the request which has been dispatched by Layer 1(F5)