The document discusses strategies for building scalable web sites, including using caching technologies like Memcached, database replication and sharding, and load balancing. It provides recommendations for hardware, software architectures, and technologies to use at different stages of a site's growth to scale efficiently. Tips are also given for optimizing performance through caching, splitting content delivery, and other best practices.

1. Experience in Building Scalable Web Sites through Infrastructure's Aspect Barcamp Bangkok 3 May 23-24, 2009 Sripathum University

2. Gen#1 Web + DB Cost effective for startup

3. Gen#2 Web After boom!! DB

4. Gen#3 Web More boom!!, add more web servers but DB is the problem DB Web Web

5. Gen#4 Web Replication could save your life for a while DB Web Web DB Replication WRITE Query READ ONLY

6. Gen#... Memcached: reduce READ query at DB Reverse Proxy: serves static contents DB Web Reverse Proxy DB Replication Memcached Memcached Web Reverse Proxy WRITE Query READ ONLY

7. Finally: Horizontal Scaling masterA Reverse Proxy Replication Reverse Proxy Web (dynamic) Web (dynamic) masterB Global Database - Multimaster Slave 1 Slave 2 UserDB1 UserDB2 UserDB3 UserDB..n Memcached

9. Software architecture

10. OS

11. Web Server

12. Caching

13. DB

14. Infra: dns, network, storage, firewall, security process, log, backup, ntp, logging, source control, monitoring, ...

15. Good to Know 80% of the end-user response time is spent on the front-end Ref: developer.yahoo.com

17. Enable GZIP

18. Add “Cache-Control” HTTP header

19. Put stylesheet at the top

20. Put scripts at the bottom

21. ............... more at developer.yahoo.com

26. Software architecture

27. OS

28. Web Server

29. Caching

30. DB

31. Infra: dns, network, storage, firewall, security process, log, backup, ntp, logging, source control, monitoring, ...

33. DB Server: Raid 1+0, SAS, SCSI, FC (15K)

34. Prefer 64 bits

35. Battery-backed write cache could improve disk I/O performance

36. We have HP BL20p, BL25p, BL460c, DL380 G3 G5, DL360 G3 G5 … Dell PE, Dell R300

37. Out of band management is required

39. Foundry ServerIron GTE, G4 (now Brocade)

43. Choose any os. that you can fully control it

46. Comment unused modules

50. MyISAM, table locking

52. Enterprise features

54. Index hitting for SELECT ?

55. Query monitoring

60. Apache Mod_Proxy (never tried)

61. Varnish (good response time, only UTF8)

63. SAN is not for sharing across servers

66. Caching Caching & Caching

68. Very good performance

70. Slow

71. Painful for operation

73. Build on commodity hardware

75. May suitable for logging application

76. Good for batch processing

78. Perform security audit if you can

79. DNS blacklist monitoring

80. Try network scan for ports changed

81. Default: DENY policy

83. Never used Memcache

86. Find “one click deployment system”

87. All servers must sync their clock

88. Centralize log server + Analyzer

89. Backup & restore

90. Perform URL monitoring from outside & inside

91. Try ITIL V3 to improve the quality of IT services

92. Twitter: @AuntiSpam