Large-scale websites performance optimisation tricks. Airline case study. @ZendCon

Practical lessons learned while revamping a US airline website to resist huge Black Friday and Cyber Monday traffic values. Using HTTP status codes and PHP cleverly, we have made parallel requests possible, so that the user experience is greatly enhanced, and we pre-cache resource-consuming user searches. All on a solid PHP foundation.

Transcript

1. LARGE-SCALE WEBSITES PERFORMANCE OPTIMISATION TRICKS Georgiana Gligor / @gbtekkie Airline case study
2. 2 ✤ Geek. Mother. Do-er. ✤ Crafting enterprise apps ✤ Large-Scale Application Architect ✤ PHP Cluj Meetup Organiser ✤ Systems Engineering PhD Student Georgiana Gligor @gbtekkie gb@tekkie.ro
3. The Challenge Enterprise Architecture The Tricks Lessons Learned OUTLINE 3
4. THE CHALLENGE
5. ✤ ultra low cost airline ✤ clever airports strategy ✤ own reservation system (no GDS) ✤ selling models: site, call centre 5 THE CHALLENGE
6. 6 TODAY
7. 7 LEGACY
8. ✤ destination-centred travel experience ✤ scalability ✤ withstand Cyber Monday test ✤ narrow delivery timeframe 8 REQUIREMENTS
9. 9 CONSTRAINTS https://youtu.be/MQm5BnhTBEQ
10. CONSTRAINTS 10
11. 11 CONSTRAINTS
12. (1) booking path (2) online check-in (3) Cyber Monday preparation 12 MILESTONES
13. ENTERPRISE ARCHITECTURE
14. 14 Legacy as data LEGACY AS DATA
15. 15 RESTful services access data CONTENT REPOSITORIES
16. 16 ISOLATE HIGH-TRAFFIC
17. 17 ISOLATE HIGH-TRAFFIC
18. 18 Web-facing components HIGH-TRAFFIC COMPONENTS
19. THE TRICKS
20. 20 #1: STATIC DATA
21. 21 #1: STATIC DATA
22. Parallel PHP https://flic.kr/p/53kGFW 22 #2: PARALLELISM
23. 23 Parallel PHP #2: PARALLELISM ✤ same good old cURL, but on steroids ✤ curl_init -> curl_multi_init ✤ async process multiple cURL handles
24. 24 #2: PARALLELISM
25. 25 Fixture-based development #3: FIXTURES ✤ discuss contracts before actual coding ✤ eliminates problems early on ✤ developers work independently ✤ test components separately
26. 26 #3: FIXTURES
27. 27 #4: 204 TRICK ✤ HTTP status code 204 ✤ success code ✤ Content-Length: 0 ✤ backend ack request and continues ✤ client can continue processing
28. 28 #4: 204 TRICK
29. 29 #4: 204 TRICK public function batchProcess($data) { }
30. 30 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions }
31. 31 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions // 2 - validate user data }
32. 32 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content }
33. 33 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content // 4 - process batch }
34. 34 #4: 204 TRICK
35. 35 #4: 204 TRICK
36. 36 Departments inside a company don’t work together. - Silo Mentality #5: SILOS
37. ✤ frontend (Drupal, Javascript SPAs) ✤ backend (PHP services) ✤ cache 37 #5: SILOS 1 silo = full setup of servers that deliver the end-to-end functionality
38. 38 #5: SILOS
39. 39 #5: SILOS
40. 40 #5: SILOS
41. 41 #5: SILOS
42. 42 #5: SILOS
43. 43 #5: SILOS
44. 44 #5: SILOS
45. 45 #5: SILOS
46. 46 #5: SILOS
47. LESSONS LEARNED
48. ✤ static data ✤ parallelism ✤ fixtures ✤ 204 trick ✤ silos 48
49. Q & A @gbtekkie https:/ /joind.in/talk/d9f66
50. Georgiana Gligor 50 THANK YOU