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

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 Symfony2 foundation.

Transcript

2. ‹#› Music City Code 2016 Airline Case Study LARGE-SCALE WEBSITES PERFORMANCE OPTIMISATION TRICKS @gbtekkie
3. 3 ✤ Geek. Mother. Do-er. ✤ Crafting enterprise- level apps ✤ on LAMP stack since 2003 ✤ Architecture and DevOps consultant ✤ PHP Cluj Meetup Organizer Georgiana Gligor
4. The Challenge Enterprise Architecture The Tricks Lessons Learned OUTLINE 4
5. THE CHALLENGE
6. ✤ ultra low cost airline ✤ clever airports strategy ✤ own reservation system (no GDS) ✤ selling models: site, call centre 6 THE CHALLENGE
7. 7 LEGACY
8. ✤ destination-centred travel experience ✤ scalability ✤ withstand Cyber Monday test ✤ narrow delivery timeframe 8 REQUIREMENTS
9. ✤ polyglot technology stack • Java • LAMP ✤ geographically distributed teams • 10 timezones ✤ replace legacy monolith 9 CONSTRAINTS
10. (1) booking path (2) online check-in (3) Cyber Monday preparation 10 MILESTONES
11. ENTERPRISE ARCHITECTURE
12. 12 Legacy as data LEGACY AS DATA
13. 13 RESTful services access data CONTENT REPOSITORIES
14. 14 ISOLATE HIGH-TRAFFIC
15. 15 Web-facing components HIGH-TRAFFIC COMPONENTS
16. THE TRICKS
17. 17 #1: STATIC DATA
18. 18 #1: STATIC DATA
19. 19 Parallel PHP #2: PARALLELISM ✤ async process multiple cURL handles ✤ same good old cURL, but on steroids ✤ curl_multi
20. 20 #2: PARALLELISM
21. 21 #3: FIXTURES
22. 22 Fixture-based development #3: FIXTURES ✤ discuss contracts before actual coding ✤ eliminates problems early on ✤ developers work independently ✤ test components separately
23. 23 #4: 204 TRICK ✤ HTTP status code 204 ✤ success code ✤ Content-Length: 0 ✤ backend ack request and continues ✤ client can continue processing
24. 24 #4: 204 TRICK
25. 25 #4: 204 TRICK public function batchProcess($data) { }
26. 26 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions }
27. 27 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions // 2 - validate user data }
28. 28 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content }
29. 29 #4: 204 TRICK public function batchProcess($data) { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content // 4 - process batch }
30. 30 #4: 204 TRICK
31. 31 #4: 204 TRICK
32. ✤ frontend (Drupal, Javascript SPAs) ✤ backend (PHP services) ✤ cache 32 #5: SILOS 1 silo = full setup of servers that deliver the end-to-end functionality
33. 33 #5: SILOS
34. 34 #5: SILOS
35. 35 #5: SILOS
36. 36 #5: SILOS
37. LESSONS LEARNED
38. ✤ static data ✤ parallelism ✤ fixtures ✤ delegate responsibility ✤ silos 38
39. Q & A g@polyglots.tech @gbtekkie
40. Georgiana Gligor 40 THANK YOU