This document discusses strategies for achieving high availability and high performance with Drupal. It recommends using redundant web and database servers, load balancers, caching with Varnish and Memcache, and a distributed file system like GlusterFS. MySQL master-slave replication is suggested for database redundancy. The goal is a scalable system with no single point of failure and fast response times.

1. Drupal
High Availability
High Performance

2. Drupal
High Availability
High Performance
How to sleep without the
server-crash-fear

3. High Availability

4. High Availability
• no „Single Point of Failure“

5. High Availability
• no „Single Point of Failure“
• Redundancy

6. High Performance

7. High Performance
• Response times

8. High Performance
• Response times
• Caching

9. High Performance
• Response times
• Caching
• HTML

10. High Performance
• Response times
• Caching
• HTML
• Data (serialized)

11. High Performance
• Response times
• Caching
• HTML
• Data (serialized)
• Scalable

12. High Performance
• Response times
• Caching
• HTML
• Data (serialized)
• Scalable
• adding easy and fast more
servers

13. Scalable & Redundancy
Server System

14. starting position

15. Goal
Varnish Varnish

16. starting position

17. Two Webserver

18. Apache/PHP

19. Apache/PHP
• APC

20. Apache/PHP
• APC
• precompiled

21. Apache/PHP
• APC
• precompiled
• keeps files in memory

22. nginx?

23. nginx?
• lightweight Webserver

24. nginx?
• lightweight Webserver
• Reverse Proxy

25. nginx?
• lightweight Webserver
• Reverse Proxy
• Loadbalander

26. nginx?
• lightweight Webserver
• Reverse Proxy
• Loadbalander
• can be faster

27. nginx?
• lightweight Webserver
• Reverse Proxy
• Loadbalander
• can be faster
• more knowledge needed

28. Two Webserver
MySQL?

29. starting position

30. dedicated MySQL

31. second Webserver

32. How to Access?
?

33. Loadbalancer

34. Loadbalancer

35. Loadbalancer
• passes through request

36. Loadbalancer
• passes through request
• „Man in the middle“

37. Loadbalancer

38. second Loadbalancer

39. second Loadbalancer
files?

40. NFS
NFS

41. NFS
NFS
fallback?

42. GlusterFS

43. GlusterFS

44. GlusterFS
• Distributed Filesystem

45. GlusterFS
• Distributed Filesystem
• multiple Server/Clients

46. GlusterFS
• Distributed Filesystem
• multiple Server/Clients
• auto-heal

47. GlusterFS
• Distributed Filesystem
• multiple Server/Clients
• auto-heal
• split-brain

48. GlusterFS
• Distributed Filesystem
• multiple Server/Clients
• auto-heal
• split-brain
• Not so fast

49. GlusterFS

50. second GlusterFS

51. MySQL
fallback?

52. MySQL Master/Slave

53. MySQL Master/Slave
• Master

54. MySQL Master/Slave
• Master
• WRITE

55. MySQL Master/Slave
• Master
• WRITE
• Slave

56. MySQL Master/Slave
• Master
• WRITE
• Slave
• READ

57. MySQL Master/Slave
• Master
• WRITE
• Slave
• READ
• Hot Spare

58. MySQL Master/Slave
• Master
• WRITE
• Slave
• READ
• Hot Spare
• Slave becomes Master

59. MySQL

60. MySQL

61. Memcache
memcache?

62. memcache

63. memcache
• Replaces “_cache“ tables

64. memcache
• Replaces “_cache“ tables
• Key / Value Store

65. memcache
• Replaces “_cache“ tables
• Key / Value Store
• Fast

66. memcache
• Replaces “_cache“ tables
• Key / Value Store
• Fast
• Memory only

67. memcache
• Replaces “_cache“ tables
• Key / Value Store
• Fast
• Memory only
• own Server

68. Memcache

69. Varnish
Varnish Varnish

70. Varnish

71. Varnish
• Reverse Proxy

72. Varnish
• Reverse Proxy
• Hates Cookies/Sessions

73. Varnish
• Reverse Proxy
• Hates Cookies/Sessions
• No SSL

74. Varnish
• Reverse Proxy
• Hates Cookies/Sessions
• No SSL
• Drupal 6

75. Varnish
• Reverse Proxy
• Hates Cookies/Sessions
• No SSL
• Drupal 6
• Pressflow

76. Varnish
• Reverse Proxy
• Hates Cookies/Sessions
• No SSL
• Drupal 6
• Pressflow
• Drupal 7/8

77. Varnish
• Reverse Proxy
• Hates Cookies/Sessions
• No SSL
• Drupal 6
• Pressflow
• Drupal 7/8
• in Core

78. tadaa!
Varnish Varnish

79. Questions!
Michael Schmid
michael@amazeelabs.com
@schnitzel