Pro Yearly is on sale from $80 to $50! »

Pushing the limits of PHP (SymfonyLive Berlin)

Pushing the limits of PHP (SymfonyLive Berlin)

It's 2019 and times have changed – yet PHP is still most often associated with your average product catalog or blogging platform. In this talk you will learn that PHP's huge ecosystem has way more to offer and PHP is not inferior at all to its evil cousin Node.js.

You will learn about the core concepts of async PHP and why you too should care about ReactPHP being a real thing. The talk has a strong focus on sparking the idea that PHP can be way faster and more versatile than you probably thought. Bring along an open mind, and through lots of interesting examples and live demos learn why what sounds crazy at first might soon be a valuable addition in your toolbox.

D1b6700884ac0ae368918ad171bb6a75?s=128

Christian Lück

September 27, 2019
Tweet

Transcript

  1. pushing the limits of PHP @another_clue

  2. pushing the limits of PHP why ReactPHP is awesome and

    why YOU should care @another_clue
  3. Agenda - Hello! - PHP, the web of the ‘90s?

    - Enter React - Core components - Examples and demo time - Conclusions 3
  4. Hello! 4

  5. $ whoami 5

  6. $ whoami Christian Lück 6

  7. $ whoami Christian Lück 7

  8. $ whoami Christian Lueck 8

  9. $ whoami Christian Lueck 9

  10. $ whoami Christian Lueck @clue 10

  11. $ whoami Christian Lueck @another_clue 11

  12. $ whoami Christian Lueck @another_clue passionate about pushing the limits

    12
  13. $ whoami Christian Lueck @another_clue passionate about pushing the limits

    freelance software engineer 13
  14. Who are you? 14 now that you know me…

  15. Who are you? 15 now that you know me… -

    PHP developers? - architects / engineers?
  16. Who are you? 16 now that you know me… -

    PHP developers? - architects / engineers? - know React?
  17. PHP, the web of the ‘90s? 17

  18. PHP and the web of the ‘90s 18

  19. PHP and the web of the ‘90s 19 Apache Client

    PHP MySQL
  20. PHP and the web of the ‘90s traditional LAMP stack

    20 Apache Client PHP MySQL
  21. PHP and the web of the ‘90s traditional LAMP stack

    Request-Response-Cycle 21 Apache Client PHP MySQL
  22. PHP and the web of the ‘90s traditional LAMP stack

    Request-Response-Cycle PHP is too slow? 22 Apache Client PHP MySQL
  23. PHP and the web of the ‘90s traditional LAMP stack

    Request-Response-Cycle PHP is too slow? 23 Apache Client MySQL FPM PHP PHP
  24. PHP and the web of the ‘90s traditional LAMP stack

    Request-Response-Cycle PHP is too slow? 24 nginx Client MySQL FPM PHP PHP
  25. PHP and the web of the ‘90s traditional LAMP stack

    Request-Response-Cycle PHP is too slow? 25 nginx Client FPM PHP PHP memcache MySQL
  26. PHP may not be pretty… 26

  27. PHP may not be pretty… but it gets the job

    done! 27
  28. Knock knock! Who’s there? 28

  29. Knock knock! 2019! Who’s there? 29

  30. Knock knock! 2019! - Separation of concerns (Frontend↔Backend) - HTTP

    APIs (RESTful) - Integration with 3rd parties - Live-Data (ticker) - CLI tools Who’s there? 30
  31. Node.js 31

  32. Node.js 32 good fit, huge ecosystem

  33. Node.js 33 good fit, huge ecosystem interesting concepts

  34. Node.js 34 good fit, huge ecosystem interesting concepts npm install…

  35. nodejs? 35

  36. no js! 36

  37. Everybody’s favorite language… 37

  38. PHP 38

  39. PHP 39 gets the job done

  40. PHP 40 gets the job done widespread usage

  41. PHP 41 gets the job done widespread usage if PHP

    can do it…
  42. Enter React! 42

  43. 43

  44. The other React™ 44

  45. The REAL React™ 45

  46. 46

  47. What is React? 47

  48. What is React? non-blocking I/O 48

  49. What is React? non-blocking I/O event-driven 49

  50. What is React? non-blocking I/O event-driven async 50

  51. 100% 51

  52. 100% pure PHP 52

  53. 100% pure PHP no extensions 53

  54. 100% pure PHP no extensions no magic 54

  55. What does that even mean?! 55

  56. the idea 56

  57. calculations are fast 57 the idea

  58. calculations are fast I/O is slow 58 the idea

  59. I/O is everywhere 59

  60. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you

    name it…) 60
  61. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you

    name it…) mysql, postgres 61
  62. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you

    name it…) mysql, postgres filesystem I/O (session files) 62
  63. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you

    name it…) mysql, postgres filesystem I/O (session files) redis, memcache 63
  64. 64 Source: Latency Numbers Every Programmer Should Know: https://gist.github.com/jboner/2841832 CPU

    vs I/O
  65. I/O is slow! 65

  66. I/O is slow! So why wait? 66

  67. This is React 67

  68. This is React 68 Start multiple I/O operations (non-blocking)

  69. This is React 69 Start multiple I/O operations (non-blocking) Get

    notified when something happens (react)
  70. This is React 70 Start multiple I/O operations (non-blocking) Get

    notified when something happens (react) Don’t waste time waiting
  71. What React is not 71

  72. What React is not React is not black magic /

    vodoo 72
  73. What React is not React is not black magic /

    vodoo React is not a framework 73
  74. What React is not React is not black magic /

    vodoo React is not a framework React is not the new buzz 74
  75. React core components 75

  76. React Core components - Event loop (reactor) - Streams -

    Promises 76
  77. Event loop Consumers - THE core, low-level component 77

  78. Event loop Consumers - THE core, low-level component - Create

    an instance - Just use the Factory - Additional extensions for bigger payloads - something inbetween… - just pass the $loop around - Start running - keeps running forever - unless stopped or done 78
  79. Event loop Consumers - THE core, low-level component - Create

    an instance - Just use the Factory - Additional extensions for bigger payloads - something inbetween… - just pass the $loop around - Start running - keeps running forever - unless stopped or done 79 $loop = Factory::create(); // something inbetween // pass the $loop around to all components $loop->run();
  80. Event loop Implementors - Reactor pattern (hence the name) 80

  81. Event loop Implementors - Reactor pattern (hence the name) -

    start timers - once - periodic - ticks 81 $loop->addTimer(0.5, function () { echo ‘world’; }); $loop->addTimer(0.3, function () { echo ‘hello’; });
  82. Event loop Implementors - Reactor pattern (hence the name) -

    start timers - once - periodic - ticks - wait for stream resources to become - readable - writable 82 $loop->addTimer(0.5, function () { echo ‘world’; }); $loop->addTimer(0.3, function () { echo ‘hello’; }); $loop->addReadStream($stream, $fn); $loop->addWriteStream($stream, $fn);
  83. Streams - Process large strings in chunks as they happen

    (think downloads) - Types - Readable (e.g. STDIN pipe) - Writable (e.g. STDOUT pipe) - Duplex (e.g. TCP/IP connection) 83
  84. Streams - interfaces, events and listeners: 84 $dest->write(‘hello’); $source->on(‘data’, function

    ($data) { var_dump($data); }); $source->on(‘close’, function () { echo ‘stream closed’; });
  85. Streams - interfaces, events and listeners: 85 $dest->write(‘hello’); $source->on(‘data’, function

    ($data) { var_dump($data); }); $source->on(‘close’, function () { echo ‘stream closed’; }); $source->pipe($gunzip)->pipe($badwords)->pipe($dest);
  86. Promises - Placeholder for a single future result - Possible

    states: - pending - fulfilled (successfully resolved) - rejected (Exception occured) 86
  87. Promises - no more imperative code flow - instead (tell,

    don’t ask) 87 $a->then($fulfilled = null, $rejected = null); $a->then(‘process’); $a->then(‘process’, ‘var_dump’);
  88. Examples and demo time! 88

  89. Examples and demo time! All open source with links 89

  90. Socket server 90 react/socket - THE canonical chat example -

    broadcast all incoming msgs
  91. Socket server 91 react/socket - THE canonical chat example -

    broadcast all incoming msgs - run example server - connect via telnet: $ telnet live.clue.engineering 8000
  92. 92

  93. HTTP client 93 clue/buzz-react - Simple HTTP requests - inspired

    by kriswallsmith/buzz - PSR-7 compatible
  94. HTTP client 94 clue/buzz-react - Simple HTTP requests - inspired

    by kriswallsmith/buzz - PSR-7 compatible - Promises and Streams - It’s fast…
  95. HTTP client 95 clue/buzz-react - Simple HTTP requests - inspired

    by kriswallsmith/buzz - PSR-7 compatible - Promises and Streams - It’s fast… - benchmarks in following slides about clue/docker-react
  96. Packagist API clue/packagist-api-react - get information about any Composer package

    - simple, Promise-based - lightweight wrapper between - KnpLabs/packagist-api - clue/buzz-react 96
  97. Packagist API clue/packagist-api-react - get information about any Composer package

    - simple, Promise-based - lightweight wrapper between - KnpLabs/packagist-api - clue/buzz-react 97 - see its examples $ php examples/search.php
  98. Docker client clue/docker-react - Run apps in isolated containers -

    “build, ship and run, anywhere” - Controlled through HTTP API - Promises and Streams 98
  99. Docker client clue/docker-react - Run apps in isolated containers -

    “build, ship and run, anywhere” - Controlled through HTTP API - Promises and Streams 99 - see its promise examples $ php examples/info.php - see its streaming examples $ php examples/benchmark-exec.php
  100. 2400 MB/s 100

  101. 2400 MB/s 101

  102. 2400 MB/s 102 dockerd maxed out PHP not

  103. HTTP server react/http - Pure PHP, with no additional webserver

    - standard PSR-7 interfaces 103
  104. HTTP server react/http - Pure PHP, with no additional webserver

    - standard PSR-7 interfaces - Lots of third-party integrations with traditional frameworks (Symfony, Slim etc.) 104
  105. 11k requests/s 105

  106. 11k requests/s 106

  107. 11k requests/s 107 this is a local, single core benchmark!

  108. 11k requests/s 108 this is a local, single core benchmark!

    quad core i7 + HT => ~88k requests/s
  109. 11k requests/s 109 this is a local, single core benchmark!

    quad core i7 + HT => ~88k requests/s 40M requests/h (single core)
  110. 11k requests/s 110 this is a local, single core benchmark!

    quad core i7 + HT => ~88k requests/s 40M requests/h (single core) ~300M requests/h
  111. Server sent events clue/sse-react - Server sent events (SSE) -

    aka. EventSource (browser API) - Streaming events to browser - limited browser support 111
  112. Server sent events clue/sse-react - Server sent events (SSE) -

    aka. EventSource (browser API) - Streaming events to browser - limited browser support 112 - see examples connecting to initial chat $ php examples/chat-server.php - open browser: http://live.clue.engineering:8080/
  113. 113

  114. Websocket server cboden/ratchet - Async WebSocket server - bidirectional data

    flow between browser and server - better browser support 114
  115. Redis client 115 clue/redis-react - Redis is a fast in-memory

    DB - very simple commands - very simple protocol - pipelined, Promise-based
  116. Redis client 116 clue/redis-react - Redis is a fast in-memory

    DB - very simple commands - very simple protocol - pipelined, Promise-based - see its examples $ php examples/incr.php
  117. Redis server 117

  118. Redis server 118 - Official Redis is written in C

  119. Redis server 119 clue/php-redis-server - Official Redis is written in

    C - Reimplementation is pure PHP
  120. Redis server 120 clue/php-redis-server - Official Redis is written in

    C - Reimplementation is pure PHP - Very simple to add commands
  121. Redis server 121 clue/php-redis-server - Official Redis is written in

    C - Reimplementation is pure PHP - Very simple to add commands - How fast could PHP possibly be? Let’s see…
  122. Redis server 122 clue/php-redis-server - Official Redis is written in

    C - Reimplementation is pure PHP - Very simple to add commands - How fast could PHP possibly be? Let’s see… - see its bin $ php bin/redis-server.php - test via clue/redis-react - test via official redis CLI - run official redis benchmark during talk: - official server: ~150k OP/s
  123. 100k OP/s 123

  124. 100k OP/s 124

  125. 100k OP/s pure PHP 125

  126. 100k OP/s pure PHP who needs native code anyway? 126

  127. Redis framework 127 clue/php-redis-framework - Development preview - Very simple

    to add custom commands
  128. Redis framework 128 clue/php-redis-framework - Development preview - Very simple

    to add custom commands - run example server $ php examples/11-beer.php - connect via telnet: $ telnet IP 9000
  129. 129

  130. Quassel clue/quassel-react - Quassel IRC core - event-driven IRC chatbots

    - re-using existing identity 130
  131. 131

  132. Zenity clue/zenity-react - PHP desktop GUI applications - very simple,

    Promise-based 132
  133. Zenity clue/zenity-react - PHP desktop GUI applications - very simple,

    Promise-based 133 - see its simple examples $ php examples/01-dialog.php - see its more realistic examples $ php examples/06-menu.php $ php examples/03-progress-pulsate.php $ php examples/03-progress-random.php
  134. 134

  135. 135

  136. 136

  137. BunnyPHP bunny/bunny - AMQP (RabbitMQ) - job worker processes -

    run slow things in background 137
  138. no polling 138

  139. no polling 139 jobs instantly picked up

  140. no polling 140 jobs instantly picked up thousands of jobs

    per second
  141. no polling 141 jobs instantly picked up thousands of jobs

    per second concurrently processing hundreds or more
  142. many, MANY more third-party projects: https://github.com/reactphp/react/wiki/Users 142

  143. Conclusions 143

  144. 144 Can I use ReactPHP to make my website 1000x

    faster?
  145. YES 145 Can I use ReactPHP to make my website

    1000x faster?
  146. YES 146 But you might be missing the point… Can

    I use ReactPHP to make my website 1000x faster?
  147. PHP 147

  148. PHP faster than you probably thought 148

  149. PHP faster than you probably thought more versatile than you

    probably thought 149
  150. ReactPHP 150

  151. ReactPHP 151 a real deal and here to stay

  152. ReactPHP 152 a real deal and here to stay stable

    & production ready
  153. ReactPHP 153 a real deal and here to stay stable

    & production ready *awesome*
  154. try! 154

  155. try! whenever having to wait 155

  156. try! whenever having to wait whenever accessing network 156

  157. help! 157

  158. help! elaborate documentation on ReactPHP.org 158

  159. help! elaborate documentation on ReactPHP.org tweet @ReactPHP or #reactphp 159

  160. help! elaborate documentation on ReactPHP.org tweet @ReactPHP or #reactphp Talk

    to me 160
  161. help! elaborate documentation on ReactPHP.org tweet @ReactPHP or #reactphp Talk

    to me Did I mention I’m available? 161
  162. // thank you! $loop->stop(); 162 @another_clue – https://clue.engineering/

  163. integration 163

  164. integration non-blocking and blocking don’t mix well 164

  165. integration non-blocking and blocking don’t mix well decide for either

    approach 165
  166. integration non-blocking and blocking don’t mix well decide for either

    approach isolate & communicate 166
  167. Integration with traditional environments 167 integrating async into sync is

    easy
  168. Integration with traditional environments 168 integrating async into sync is

    easy - just run the loop until you’re done - see clue/block-react
  169. Integration with traditional environments 169 integrating async into sync is

    easy - just run the loop until you’re done - see clue/block-react integrating sync into async is hard
  170. Integration with traditional environments 170 integrating async into sync is

    easy - just run the loop until you’re done - see clue/block-react integrating sync into async is hard - often requires async rewrite - consider forking instead
  171. Avoid blocking! - The loop must not be blocked 171

  172. Avoid blocking! - The loop must not be blocked -

    Many functions / lib assume blocking by default - Anything >1ms should be reconsidered 172
  173. Avoid blocking! - The loop must not be blocked -

    Many functions / lib assume blocking by default - Anything >1ms should be reconsidered - Alternatives - Single result: Promises - Evented: Streams 173
  174. Avoid blocking! - The loop must not be blocked -

    Many functions / lib assume blocking by default - Anything >1ms should be reconsidered - Alternatives - Single result: Promises - Evented: Streams - Need a blocking function? - Fork off! - Use IPC 174
  175. Avoid blocking! - The loop must not be blocked -

    Many functions / lib assume blocking by default - Anything >1ms should be reconsidered - Alternatives - Single result: Promises - Evented: Streams - Need a blocking function? - Fork off! - Use IPC 175 Pay attention: - PDO, mysql etc. - file system access - network access - third-party APIs