Pushing the limits with ReactPHP (PHPDD17)

It’s 2017 and times have changed – yet PHP is still most often associated with your average product catalogue 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 examples and demos learn why what sounds crazy at first might soon be a valuable addition in your toolbox.

Transcript

1. pushing the limits with ReactPHP why ReactPHP is awesome and why YOU should care
2. Agenda - Hello! - PHP, the web of the ‘90s? - Enter React - Core components - Examples and demo time - Conclusions 2
3. Hello! 3
4. $ whoami Christian Lück 4
5. $ whoami Christian Lueck 5
6. $ whoami Christian Lueck 6
7. $ whoami Christian Lueck @clue 7
8. $ whoami Christian Lueck @another_clue 8
9. $ whoami Christian Lueck @another_clue passionate about pushing the limits 9
10. $ whoami Christian Lueck @another_clue passionate about pushing the limits freelance software engineer 10
11. Who are you? 11 now that you know me…
12. Who are you? 12 now that you know me… - PHP developers? - architecs / engineers?
13. Who are you? 13 now that you know me… - PHP developers? - architecs / engineers? - know React?
15. The other React™ 15
16. The one without licensing issues 16
17. The REAL React™ 17
18. PHP, the web of the ‘90s? 18
19. PHP and the web of the ‘90s - traditional LAMP stack - Request-Response-Cycle - PHP is too slow? 19 Apache Client PHP MySQL
20. PHP and the web of the ‘90s - traditional LAMP stack - Request-Response-Cycle - PHP is too slow? - We sure can improve this… 20 Apache Client PHP MySQL
21. PHP and the web of the ‘90s - traditional LAMP stack - Request-Response-Cycle - PHP is too slow? - We sure can improve this… 21 Apache Client PHP MySQL Apache Client FPM MySQL PHP PHP
22. PHP and the web of the ‘90s - traditional LAMP stack - Request-Response-Cycle - PHP is too slow? - We sure can improve this… 22 Apache Client PHP MySQL Apache Client FPM MySQL PHP PHP nginx Client FPM MySQL PHP PHP
23. PHP and the web of the ‘90s - traditional LAMP stack - Request-Response-Cycle - PHP is too slow? - We sure can improve this… 23 Apache Client PHP MySQL Apache Client FPM MySQL PHP PHP nginx Client FPM MySQL PHP PHP nginx Client FPM memcache PHP PHP MySQL
24. PHP may not be pretty… 24
25. PHP may not be pretty… but it gets the job done! 25
26. Knock knock! Who’s there? 26
27. Knock knock! 2017! Who’s there? 27
28. Knock knock! 2017! - Separation of concerns (Frontend↔Backend) - HTTP APIs (RESTful) - Integration with 3rd parties - Live-Data (ticker) - CLI tools Who’s there? 28
29. nodejs? 29
30. no js! 30
31. Enter React! 31
32. What is React? 32
33. What is React? non-blocking I/O 33
34. What is React? non-blocking I/O event-driven 34
35. What is React? non-blocking I/O event-driven async 35
36. 100% 36
37. 100% pure PHP 37
38. 100% pure PHP no extensions 38
39. 100% pure PHP no extensions no magic 39
40. What does that even mean?! 40
41. the idea 41
42. the idea calculations are fast 42
43. the idea calculations are fast I/O is slow 43
44. I/O is everywhere 44
45. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you name it…) 45
46. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you name it…) mysql, postgres 46
47. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you name it…) mysql, postgres filesystem I/O (session files) 47
48. I/O is everywhere third party HTTP APIs (RESTful, SOAP, you name it…) mysql, postgres filesystem I/O (session files) redis, memcache 48
49. 49 Source: Latency Numbers Every Programmer Should Know: https://gist.github.com/jboner/2841832 CPU vs I/O
50. I/O is slow! 50
51. I/O is slow! So why wait? 51
52. This is React 52
53. This is React 53 Start multiple I/O operations (non-blocking)
54. This is React 54 Start multiple I/O operations (non-blocking) Get notified when something happens (react)
55. This is React 55 Start multiple I/O operations (non-blocking) Get notified when something happens (react) Don’t waste time waiting
56. What React is not 56
57. What React is not React is not black magic / vodoo 57
58. What React is not React is not black magic / vodoo React is not a framework 58
59. What React is not React is not black magic / vodoo React is not a framework React is not the new buzz 59
60. React core components 60
61. React Core components - Event loop (reactor) - Streams - Promises 61
62. Event loop Consumers - THE core, low-level component 62
63. 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 63
64. 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 64 $loop = Factory::create(); // something inbetween // pass the $loop around to all components $loop->run();
65. Event loop Implementors - Reactor pattern (hence the name) 65
66. Event loop Implementors - Reactor pattern (hence the name) - start timers - once - periodic - ticks 66 $loop->addTimer(0.5, function () { echo ‘world’; }); $loop->addTimer(0.3, function () { echo ‘hello’; });
67. Event loop Implementors - Reactor pattern (hence the name) - start timers - once - periodic - ticks - wait for stream resources to become - readable - writable 67 $loop->addTimer(0.5, function () { echo ‘world’; }); $loop->addTimer(0.3, function () { echo ‘hello’; }); $loop->addReadStream($stream, $fn); $loop->addWriteStream($stream, $fn);
68. 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) 68
69. Streams - interfaces, events and listeners: 69 $dest->write(‘hello’); $source->on(‘data’, function ($data) { var_dump($data); }); $source->on(‘close’, function () { echo ‘stream closed’; });
70. Streams - interfaces, events and listeners: 70 $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);
71. Promises - Placeholder for a single future result - Possible states: - pending - fulfilled (successfully resolved) - rejected (Exception occured) 71
72. Promises - no more imperative code flow - instead (tell, don’t ask) 72 $a->then($fulfilled = null, $rejected = null); $a->then(‘process’); $a->then(‘process’, ‘var_dump’);
73. Examples and demo time! 73
74. Socket server 74 react/socket - THE canonical chat example - broadcast all incoming msgs
75. Socket server 75 react/socket - THE canonical chat example - broadcast all incoming msgs - run example server - connect via telnet: $ telnet clue.engineering 6001
77. HTTP client 77 clue/buzz-react - Simple HTTP requests - inspired by kriswallsmith/buzz - PSR-7 compatible
78. HTTP client 78 clue/buzz-react - Simple HTTP requests - inspired by kriswallsmith/buzz - PSR-7 compatible - Promises and Streams - It’s fast…
79. HTTP client 79 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
80. Packagist API clue/packagist-api-react - get information about any Composer package - simple, Promise-based - lightweight wrapper between - KnpLabs/packagist-api - clue/buzz-react 80
81. Packagist API clue/packagist-api-react - get information about any Composer package - simple, Promise-based - lightweight wrapper between - KnpLabs/packagist-api - clue/buzz-react 81 - see its examples $ php examples/search.php
82. Docker client clue/docker-react - Run apps in isolated containers - “build, ship and run, anywhere” - Controlled through HTTP API - Promises and Streams 82
83. Docker client clue/docker-react - Run apps in isolated containers - “build, ship and run, anywhere” - Controlled through HTTP API - Promises and Streams 83 - see its promise examples $ php examples/info.php - see its streaming examples $ php examples/benchmark-exec.php
84. 700 MiB/s 84
85. 700 MiB/s 85
86. 700 MiB/s 86 dockerd maxed out PHP not
87. HTTP server react/http - Pure PHP, with no additional webserver - standard PSR-7 interfaces 87
88. HTTP server react/http - Pure PHP, with no additional webserver - standard PSR-7 interfaces - Lots of third-party integrations with traditional frameworks (symfony, slim, silex, PIMF etc.) 88
89. 5k requests/s 89
90. 5k requests/s 90
91. 5k requests/s 91 this is a local single core benchmark!
92. 5k requests/s 92 this is a local single core benchmark! dual core i3 => 10k requests/s
93. 5k requests/s 93 this is a local single core benchmark! dual core i3 => 10k requests/s 36M requests/h
94. Server sent events clue/sse-react - Server sent events (SSE) - aka. EventSource (browser API) - Streaming events to browser - limited browser support 94
95. Server sent events clue/sse-react - Server sent events (SSE) - aka. EventSource (browser API) - Streaming events to browser - limited browser support 95 - see examples connecting to initial chat $ php examples/chat-server.php - open browser: http://clue.engineering:7000/
97. Websocket server cboden/ratchet - Async WebSocket server - bidirectional data flow between browser and server - better browser support 97
98. Redis client 98 clue/redis-react - Redis is a fast in-memory DB - very simple commands - very simple protocol - pipelined, Promise-based
99. Redis client 99 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
100. Redis server 100
101. Redis server 101 - Official Redis is written in C
102. Redis server 102 clue/php-redis-server - Official Redis is written in C - Reimplementation is pure PHP
103. Redis server 103 clue/php-redis-server - Official Redis is written in C - Reimplementation is pure PHP - Very simple to add commands
104. Redis server 104 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…
105. Redis server 105 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: ~90k OP/s
106. 50k OP/s 106
107. 50k OP/s 107
108. 50k OP/s pure PHP who needs native code anyway? 108
109. Redis framework 109 clue/php-redis-framework - Development preview - Very simple to add custom commands
110. Redis framework 110 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
112. Zenity clue/zenity-react - PHP desktop GUI applications - very simple, Promise-based 112
113. Zenity clue/zenity-react - PHP desktop GUI applications - very simple, Promise-based 113 - 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
117. many, MANY more third-party projects: https://github.com/reactphp/react/wiki/Users 117
118. Conclusions 118
119. PHP 119
120. PHP faster than you probably thought 120
121. PHP faster than you probably thought more versatile than you probably thought 121
122. ReactPHP 122
123. ReactPHP 123 a real deal and here to stay
124. ReactPHP 124 a real deal and here to stay stable & production ready
125. ReactPHP 125 a real deal and here to stay stable & production ready *awesome*
126. try! 126
127. try! whenever having to wait 127
128. try! whenever having to wait whenever accessing network 128
129. Need help? Want to help? - check each component’s README - check open issues 129
130. Need help? Want to help? - check each component’s README - check open issues - join #reactphp on irc.freenode.org - tweet @ReactPHP or #reactphp 130
131. Need help? Want to help? - check each component’s README - check open issues - join #reactphp on irc.freenode.org - tweet @ReactPHP or #reactphp - Talk to me 131
132. Need help? Want to help? - check each component’s README - check open issues - join #reactphp on irc.freenode.org - tweet @ReactPHP or #reactphp - Talk to me Did I mention I’m available? 132
133. // thank you! $loop->stop(); 133 @another_clue – https://lueck.tv/
134. Avoid blocking! - The loop must not be blocked 134
135. Avoid blocking! - The loop must not be blocked - Many functions / lib assume blocking by default - Anything >1ms should be reconsidered 135
136. 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 136
137. 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 137
138. 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 138 Pay attention: - PDO, mysql etc. - file system access - network access - third-party APIs
139. Integration with traditional environments 139 integrating async into sync is easy
140. Integration with traditional environments 140 integrating async into sync is easy - just run the loop until you’re done - see clue/block-react
141. Integration with traditional environments 141 integrating async into sync is easy - just run the loop until you’re done - see clue/block-react integrating sync into async is hard
142. Integration with traditional environments 142 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