Large-scale websites performance optimisation tricks @PHPUK2016

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

@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

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

@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

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 ✓ use their own reservation system (no GDS) Customer Customer

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 ✓ use their own reservation system (no GDS) ✓ selling models: website, call-centre Customer Customer

@gbtekkie PHP UK | February 2016 Legacy

@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

@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

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

@gbtekkie PHP UK | February 2016 TECHNOLOGY STACK

@gbtekkie PHP UK | February 2016 Legacy as data

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

@gbtekkie PHP UK | February 2016 Isolate high traffic

@gbtekkie PHP UK | February 2016 Web-facing components

@gbtekkie PHP UK | February 2016 WELCOME SILOS

@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

@gbtekkie PHP UK | February 2016 Silo diagram

@gbtekkie PHP UK | February 2016 STATIC DATA

@gbtekkie PHP UK | February 2016 Static data

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

@gbtekkie PHP UK | February 2016 ANATOMY OF A SILO

@gbtekkie PHP UK | February 2016 The pieces

@gbtekkie PHP UK | February 2016 Data access

@gbtekkie PHP UK | February 2016 Data caching

@gbtekkie PHP UK | February 2016 FIXTURES

@gbtekkie PHP UK | February 2016 Fixtures

@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

@gbtekkie PHP UK | February 2016 THE 204 TRICK

@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

@gbtekkie PHP UK | February 2016 204 trick in action

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

batchProcessAction() { // 1 - check permissions } Batch processing example

batchProcessAction() { // 1 - check permissions // 2 - validate user data } Batch processing example

batchProcessAction() { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content } Batch processing example

batchProcessAction() { // 1 - check permissions // 2 - validate user data // 3 - return 204 No Content // 4 - process batch } Batch processing example

@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() }

@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; }

@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

@gbtekkie PHP UK | February 2016 Event logging system

@gbtekkie PHP UK | February 2016 ERROR HANDLING

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

@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

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

@gbtekkie PHP UK | February 2016 PARALLELISM

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

@gbtekkie PHP UK | February 2016 Parallelism in practice

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

@gbtekkie PHP UK | February 2016 LESSONS LEARNED

@gbtekkie PHP UK | February 2016 ✓ silos Lessons learned

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

data ✓ ﬁxtures Lessons learned

data ✓ ﬁxtures ✓ delegate responsibility Lessons learned

data ✓ ﬁxtures ✓ delegate responsibility ✓ parallelism Lessons learned

@gbtekkie PHP UK | February 2016 Q & A

THANK YOU! Georgiana Gligor @gbtekkie https://joind.in/talk/95a6e

Large-scale websites performance optimisation tricks @PHPUK2016

Large-scale websites performance optimisation tricks @PHPUK2016

More Decks by Georgiana Gligor

Other Decks in Technology

Featured

Transcript