Reading material:
Http-session:
Http://www.cnblogs.com/tankxiao/archive/2012/02/13/2342672.html
Http://www.cnblogs.com/xueyuwyz/p/3593739.html
Log:
Http://dataunion.org/12268.html
http://www.chinawebanalytics.cn/wa-server-logfile-basic-pros-and-cons/
Web services:
http://blog.csdn.net/tuantuanls/article/details/41288311
Http://job.xdnice.com/content/BiShiJingYan/2012-11/3992.htm
Dns:
Http://codefine.co/978.html
Https://www.slideshare.net/jonoxer/introduction-to-dns
http://linux.vbird.org/linux_server/0350dns.php
Browser Access process:
http://blog.csdn.net/bruce_6/article/details/39499439
Reverse proxy:
Http://www.admin10000.com/document/6186.html
https://www.zhihu.com/question/24723688
https://www.zhihu.com/question/19761434
Lazy Load:
https://www.zhihu.com/question/19703400
Https://en.wikipedia.org/wiki/Lazy_loading
Cache
http://community.brocade.com/t5/vADC-Docs/Cache-your-website-just-for-one-second/ta-p/73929
Cdn:
http://blog.csdn.net/wangqi0079/article/details/8582411
Rate Limiter:
Http://stackoverflow.com/questions/667508/whats-a-good-rate-limiting-algorithm
Https://github.com/jhurliman/node-rate-limiter
Token Bucket:
Https://en.wikipedia.org/wiki/Token_bucket
http://code.activestate.com/recipes/578659-python-3-token-bucket-rate-limit/
https://engineering.classdojo.com/blog/2015/02/06/rolling-rate-limiter/
Seconds to Kill:
Http://www.cnblogs.com/rollenholt/p/3393398.html
http://chuansong.me/n/1334017
Http://sobuhu.com/program/2013/04/07/how-to-design-seckill.html
http://jag522.iteye.com/blog/2113519
Http://mm.fancymore.com/reading/%E7%A7%92%E6%9D%80%E7%B3%BB%E7%BB%9F%E7%9A%84%E8%AE%BE%E8%AE%A1.html
Http://itindex.net/detail/53237-%E7%A7%92%E6%9D%80-%E7%B3%BB%E7%BB%9F-%E8%AE%BE%E8%AE%A1
12306:
Http://itindex.net/detail/39902-%E7%B3%BB%E7%BB%9F-%E8%AE%BE%E8%AE%A1
Http://coolshell.cn/articles/6470.html
1. What happens when you open a Google page
Page access Failure rate: Number of connection failures/total number of connections, number of users not seen on a webpage/number of users
http://blog.csdn.net/bruce_6/article/details/39499439
Impatient users
2, how to speed up a Web Access
- Reverse proxy + multi-server
- Compressed content (JS library), compressed pictures, lazy load
- Cache: Browser, ISP cache, reverse proxy, application Server cache
3, how to design a second kill system
- Qps:10 iphone,100w QPS (Bombardment Flow)
- Level Two queue
- Reduced flow
- Reduce page size
- Static page
- Agent
- Limit request Volume (Js,rate limit)
- Keep it simple
- No database: Memory and logs
- No lock
- Isolation
- No other logic for the server that is blocking the impact
- Asynchronous
- Attack
- Lottery
4, how to design a flow control system
- Request Interval
- Buckets (database, non-database)
- Queue
- Token Bucket
System design 4:web service and traffic limits