Large-scale websites performance optimisation tricks @PHPUK2016

Slide 1

Slide 1 text

AIRLINE CASE STUDY LARGE-SCALE WEBSITES PHP UK | February 2016 @gbtekkie PERFORMANCE OPTIMISATION TRICKS

Slide 2

Slide 2 text

@gbtekkie PHP UK | February 2016 Georgiana Gligor ✓ Geek. Mother. Do-er. ✓ Crafting enterprise-level applications in PHP since 2003 ✓ Architecture and DevOps consultant ✓ PHP Cluj Meetup Organizer

Slide 3

Slide 3 text

@gbtekkie PHP UK | February 2016 Customer ✓ low cost airline, similar to Ryan Air / Wizzair / EasyJet

Slide 4

Slide 4 text

@gbtekkie PHP UK | February 2016 ✓ low cost airline, similar to Ryan Air / Wizzair / EasyJet ✓ clever strategy of using airports, so that they don’t have a direct competition on 90% of their routes Customer Customer

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

@gbtekkie PHP UK | February 2016 Legacy

Slide 8

Slide 8 text

@gbtekkie PHP UK | February 2016 The wants Wanted ✓ enable end-user to purchase a full travel experience based on the destination, not just cheap plane tickets ✓ ﬂexibility ✓ scalability ✓ be in front of the competition by withstanding the Black Friday + Cyber Monday test ✓ move at the speed of a greenﬁeld project even if the business is up and running

Slide 9

Slide 9 text

@gbtekkie PHP UK | February 2016 The needs ✓ polyglot technology stack - Java reservations engine - LAMP for the web-facing part ✓ handle geographically distributed teams - 10 timezones - round-the-clock development ✓ replace legacy monolithic app Constraints

Slide 10

Slide 10 text

@gbtekkie PHP UK | February 2016 The needs (1) booking path (2) online check-in (3) Cyber Monday preparation Milestones

Slide 11

Slide 11 text

@gbtekkie PHP UK | February 2016 TECHNOLOGY STACK

Slide 12

Slide 12 text

@gbtekkie PHP UK | February 2016 Legacy as data

Slide 13

Slide 13 text

@gbtekkie PHP UK | February 2016 RESTful services access data transactional

Slide 14

Slide 14 text

@gbtekkie PHP UK | February 2016 Isolate high traffic

Slide 15

Slide 15 text

@gbtekkie PHP UK | February 2016 Web-facing components

Slide 16

Slide 16 text

@gbtekkie PHP UK | February 2016 WELCOME SILOS

Slide 17

Slide 17 text

@gbtekkie PHP UK | February 2016 1 silo = full setup of servers that run each application component and deliver the end-to-end functionality ✓ frontend (Drupal, Javascript SPAs) ✓ backend (Symfony services) ✓ cache What is a silo

Slide 18

Slide 18 text

@gbtekkie PHP UK | February 2016 Silo diagram

Slide 19

Slide 19 text

@gbtekkie PHP UK | February 2016 STATIC DATA

Slide 20

Slide 20 text

@gbtekkie PHP UK | February 2016 Static data

Slide 21

Slide 21 text

@gbtekkie PHP UK | February 2016 Optimise access to static data

Slide 22

Slide 22 text

@gbtekkie PHP UK | February 2016 ANATOMY OF A SILO

Slide 23

Slide 23 text

@gbtekkie PHP UK | February 2016 The pieces

Slide 24

Slide 24 text

@gbtekkie PHP UK | February 2016 Data access

Slide 25

Slide 25 text

@gbtekkie PHP UK | February 2016 Data caching

Slide 26

Slide 26 text

@gbtekkie PHP UK | February 2016 FIXTURES

Slide 27

Slide 27 text

@gbtekkie PHP UK | February 2016 Fixtures

Slide 28

Slide 28 text

@gbtekkie PHP UK | February 2016 ✓ enforces discussing contracts before doing actual coding ✓ helps eliminate certain problems by having them discussed in advance ✓ allows developers to work independently and run all the stack on their machine ✓ each component is independently tested Fixture-based development

Slide 29

Slide 29 text

@gbtekkie PHP UK | February 2016 THE 204 TRICK

Slide 30

Slide 30 text

@gbtekkie PHP UK | February 2016 ✓ HTTP status code 204 ✓ success code ✓ Content-Length: 0 ✓ the backend acknowledges the request and will carry on ✓ the client can continue processing The 204 trick

Slide 31

Slide 31 text

@gbtekkie PHP UK | February 2016 204 trick in action

Slide 32

Slide 32 text

@gbtekkie PHP UK | February 2016 POST /batch-process public function batchProcessAction() { } Batch processing example

Slide 33

Slide 33 text

@gbtekkie PHP UK | February 2016 POST /batch-process public function batchProcessAction() { // 1 - check permissions } Batch processing example

Slide 34

Slide 34 text

@gbtekkie PHP UK | February 2016 POST /batch-process public function batchProcessAction() { // 1 - check permissions // 2 - validate user data } Batch processing example

Slide 35

Slide 35 text

@gbtekkie PHP UK | February 2016 POST /batch-process public function batchProcessAction() { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content } Batch processing example

Slide 36

Slide 36 text

@gbtekkie PHP UK | February 2016 POST /batch-process public function batchProcessAction() { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content // 4 - process batch } Batch processing example

Slide 37

Slide 37 text

@gbtekkie PHP UK | February 2016 Close connection: raw PHP public function closeConnection() { header('HTTP/1.0 204 No Content'); header('Content-Length: 0', true); header('Content-Type: application/json', true); flush(); // or ob_flush() }

Slide 38

Slide 38 text

@gbtekkie PHP UK | February 2016 Close connection: Symfony-specific public function closeConnection(Request $request) { $response = new StreamedResponse(); $response->setStatusCode(204); $response->headers->add(array('Connection' => 'close')); $c = function () { /* do nothing */ }; $response->setCallback($c); // needs to be a valid PHP callable $response->prepare($request); // ensure compliancy with HTTP specification $response->send(); return $response; }

Slide 39

Slide 39 text

@gbtekkie PHP UK | February 2016 ✓ cheap ✓ does not impact application performance ✓ logs are searchable ✓ logs tell the story of a user’s journey ✓ greatly help debugging Event logging system

Slide 40

Slide 40 text

@gbtekkie PHP UK | February 2016 Event logging system

Slide 41

Slide 41 text

@gbtekkie PHP UK | February 2016 Event logging system

Slide 42

Slide 42 text

@gbtekkie PHP UK | February 2016 Event logging system

Slide 43

Slide 43 text

@gbtekkie PHP UK | February 2016 ERROR HANDLING

Slide 44

Slide 44 text

@gbtekkie PHP UK | February 2016 ✓ recoverable user can continue inside the booking path ✓ non-recoverable user’s checkin process can’t proceed Error types

Slide 45

Slide 45 text

@gbtekkie PHP UK | February 2016 4xx status codes ✓ 401 unauthorised ✓ 403 forbidden ✓ 409 conﬂict ✓ 413 payload too large instruct the UI where to go back Recoverable errors

Slide 46

Slide 46 text

@gbtekkie PHP UK | February 2016 ✓ 5xx status codes ✓ 500 internal server error ✓ 503 service unavailable Non-recoverable errors

Slide 47

Slide 47 text

@gbtekkie PHP UK | February 2016 PARALLELISM

Slide 48

Slide 48 text

@gbtekkie PHP UK | February 2016 ✓ asynchronously process multiple cURL handles ✓ same good old cURL, but on steroids ✓ curl_multi Parallel PHP

Slide 49

Slide 49 text

@gbtekkie PHP UK | February 2016 Parallelism in practice

Slide 50

Slide 50 text

@gbtekkie PHP UK | February 2016 Anatomy of a Symfony service

Slide 51

Slide 51 text

@gbtekkie PHP UK | February 2016 LESSONS LEARNED

Slide 52

Slide 52 text

@gbtekkie PHP UK | February 2016 ✓ silos Lessons learned

Slide 53

Slide 53 text

@gbtekkie PHP UK | February 2016 ✓ silos ✓ static data Lessons learned

Slide 54

Slide 54 text

@gbtekkie PHP UK | February 2016 ✓ silos ✓ static data ✓ ﬁxtures Lessons learned

Slide 55

Slide 55 text

@gbtekkie PHP UK | February 2016 ✓ silos ✓ static data ✓ ﬁxtures ✓ delegate responsibility Lessons learned

Slide 56

Slide 56 text

@gbtekkie PHP UK | February 2016 ✓ silos ✓ static data ✓ ﬁxtures ✓ delegate responsibility ✓ parallelism Lessons learned