An overall presentation on scaling out your system starting from a single server and many of the several options you may face.

1. Mike Willbanks Blog: http://blog.digitalstruct.com Twitter : mwillbanks IRC : lubs on freenode Scalable Architectures 101 MNPHP Feb 3, 2011

3. Web Servers

4. Database Servers

6. DNS Servers

7. CDN Servers

8. Front-End Performance

11. Load Balancing

12. Load Balancing Our Environment

15. Static

16. Least Connections

17. Source

18. IP

20. URI Parameter

21. Header

22. Cookie

23. Regular Expression

25. Pound – Said to be great for medium traffic sites.

26. Varnish – A caching solution that also does load balancing

28. Very well known

29. Handles just about every type of routing

30. Several examples online

32. Setup can be complex and take a lot of time

33. Sample HAProxy Configuration global log 127.0.0.1 local0 log 127.0.0.1 local1 notice maxconn 4096 user haproxy group haproxy daemon defaults log global mode http option httplog option dontlognull retries 3 option redispatch maxconn 2000 contimeout 5000 clitimeout 50000 srvtimeout 50000 listen localhost 0.0.0.0:80 option httpchk GET / balance roundrobin cookie SERVERID server serv1 0.0.0.0:8080 check inter 2000 rise 2 fall 5 server serv2 0.0.0.0:8080 check inter 2000 rise 2 fall 5 option httpclose stats enable stats uri /lb?stats stats realm haproxy stats auth test:test

35. Native SSL support

36. Insanely simple setup

37. Supports virtually all types of routing

39. Setup can be complex and take a lot of time

40. Sample Pound Configuration User "www-data" Group "www-data" LogLevel 1 Alive 30 Control "/var/run/pound/poundctl.socket" ListenHTTP Address 127.0.0.1 Port 80 xHTTP 0 Service BackEnd Address 127.0.0.1 Port 8080 End BackEnd Address 127.0.0.1 Port 8080 End End End

42. Farily simple setup

43. Extremely well known

44. Many online tutorials

46. If you want a WebGUI you must PAY

47. Sample Varnish Configuration backend default1 { .host = "127.0.0.1"; .port = "8080"; .probe = { .url = "/"; .interval = 5s; .timeout = 1s; .window = 5; .threshold = 3; } } backend default2 { .host = "127.0.0.1"; .port = "8080"; .probe = { .url = "/"; .interval = 5s; .timeout = 1s; .window = 5; .threshold = 3; } } director default round-robin { { .backend = default1; } { .backend = default2; } } sub vcl_recv { if (req.http.host ~ "^127.0.0.1$") { set req.backend = default; } }

50. Client IP is likely on X-forwarded-for

52. Web Servers

54. IIS

55. Nginx

56. Lighttpd

57. etc.

59. Client IP will likely be in X-forwarded-for.

60. SSL will not be in $_SERVER['HTTPS'] and HTTP_ header instead.

62. Static content could be tagged in version control.

63. Static content may need a file server / CDN / etc.

65. Remember disk is slow and the database will be a bottleneck. How about distributed caching?

67. Database Servers

72. Be warned, auto-incrementing now should change so you do not conflict.

75. All reports / read queries should go here

77. Cache Servers (not full page)

79. File Based: Files / Sqlite / etc

83. Start to cache fetches, invalidate cache on write and write new cache, always reading from the cache.

85. Server depends on the hash.

86. Hint – use the memcached pecl extension.

90. Ensure dedicated memory!

91. If you run out of memory, does it remove an old and add the new or not allow anything to come in?

92. Job Servers

93. “ Message queues and mailboxes are software-engineering components used for interprocess communication, or for inter-thread communication within the same process. They use a queue for messaging – the passing of control or of content.” http://en.wikipedia.org/wiki/Message_queue

94. Messages are Everywhere

96. Asynchronous push / pull

97. An application framework for sending and receiving messages.

98. A way to communicate between applications / systems.

99. A way to decouple components.

100. A way to offload work.

103. Can continue to create more workers Producer Message Queue Server Consumer Consumer Consumer Consumer Consumer Message Queue Server Message Queue Server Producer Producer

105. Communication between Applications / Systems

106. Image Resizing

107. Video Processing

108. Sending out Emails

109. Auto-Scaling Virtual Instances

110. Log Analysis

111. The list goes on...

114. DNS Servers

116. It's sexy, it's sweet and it is FAST!

119. Failover / Distributed

120. CNAME support

121. TXT support

122. Name Server support

123. CDN Servers

125. Free your server from serving basic files

126. Distributed servers around the globe

129. Origin Pull is great if you want to maintain all of the content in your web server.

130. PoP Push is great for storing things like user generated content.

131. Front-End Performance

133. CSS Sprites

134. GZIP

135. Cookies are evil

136. Parallel downloads (using subdomains for serving

137. HTTP Expires

139. Firebug

140. Google Page Speed

141. Google Webmaster Tools

142. Mike Willbanks Blog: http://blog.digitalstruct.com Twitter : mwillbanks IRC : lubs on freenode Questions?