The document discusses the author's experience with Node.js and its performance, emphasizing the shift from callback-based code to using promises for better readability and maintainability. It mentions the benefits of ES6 features like generators and suggests replacing Express with Koa for improved coding practices. Additionally, it highlights the author's benchmarks showing no significant performance differences in a migration from Express to Koa.

2. Aboutme
•Several production-grade node apps in the wild
•muuuf
•Up & Front
•EthPort(using what I show today)
•The others I cannot mention 
•Maintainer of named-routes, help out at CoffeeScript, bluebird and sequelize
•Berlin Node.js (550 members)
•Actually a MathsPhD

3. SomecodeI saw
CodeSchool’sBasecamp Search, Code written in RoR
And I thought “Hey, it’s really been some time since I saw such clear code in node. There’s gottabe a way!”

4. The callbackhell
“best-practice” node-equivalent

5. Can we do better?
Yes, remove error-checking by using promises. Have one error-catcher (domain) outside the controller logic.
Somewhat better -still twists your head reading it. Also, you lose variable scope as you move down the chain.

6. Coffee-Script?
Much easier on the eyes, the order of the code is still counter-intuitive.

7. This isimpossible*…
*of course you could write synchronous C extensions that would provide this, but say goodbye to performance

8. This isimpossible*…
*of course you could write synchronous C extensions that would provide this, but say goodbye to performance

9. Event Queue
The reliance on callbacks is due to what is arguably JavaScript’s best feature –its event queue. Instead of using subprocessesor threads, it processes events sequentially as they come in.
Thus, calling I/O MUST delegate back or everything will come to a halt.

10. Performance
Concurrentusers
Response time
Server CPU usage
http://blog.loadimpact.com/2013/02/01/node-js-vs-php-using-load-impact-to-visualize-node-js-efficency/
node.js

11. Performance
Concurrentusers
Response time
Server CPU usage
http://blog.loadimpact.com/2013/02/01/node-js-vs-php-using-load-impact-to-visualize-node-js-efficency/
node.js
PHP

13. So, ES6?
Gives us generators. For this discussion, they are like functions that can be paused and continued at a later point in time.
Let’s code.

14. Rememberthis?

15. This wayitworks!

16. Looks prettyneat!
VS

17. Even nexttoRails!
VS

18. Improvespromises, too

19. Improvespromises, too
VS

20. Improvespromises, too
VS

21. …andpromisescopes

22. …andpromisescopes
VS

23. …andpromisescopes
VS

24. Towrapup
•‘yield’ makes code clearer, better readable and more maintainable
•Start using this! 0.11.13 runs two of my production websites without any hiccups (0.11.14 has some edge case memory leaks)
•Use co and/or bluebird in all places, transform third- party libraries using thunkifyor bluebird’s promisify
•If possible, replace express with koa(also gives you named routes for free)
•Finally, my benchmarks of stress testing a real-life app before and after an express-to-koamigration could not measure any performance difference in terms of requests served and an increase of memory consumption by 10-15 MB. Absolutely worth it!