- Mastering Node.js(Second Edition)
- Sandro Pasquali Kevin Faaborg
- 170字
- 2021-07-02 19:28:45
Managing concurrency
Simplifying control flows has been a concern of the Node community since the very beginning of the project. Indeed, this potential criticism was one of the very first anticipated by Ryan Dahl, who discussed it at length during the talk in which he introduced Node to the JavaScript developer community.
Because deferred code execution often requires the nesting of callbacks within callbacks, a Node program can sometimes begin to resemble a sideways pyramid, also known as The Pyramid of Doom. You've seen it: deeply nested code, 4 or 5 or even more levels deep, curly braces everywhere. Apart from syntactical annoyances, you can also imagine that tracking errors across such a call stack might be difficult—if a callback at the third level throws, who is responsible for handling that error? The second level? Even if level 2 is reading a file and level 3 is querying a database? Does that make sense? It can be hard to make sense of asynchronous program flows.
- 物聯網與北斗應用
- Twilio Cookbook
- Hands-On Full Stack Development with Spring Boot 2 and React(Second Edition)
- 信息通信網絡建設安全管理概要2
- 射頻通信系統
- 物聯網與無線傳感器網絡
- Mastering TypeScript 3
- Working with Legacy Systems
- 高級網絡技術
- Hands-On Microservices with Node.js
- 一本書讀懂物聯網
- 移動物聯網:商業模式+案例分析+應用實戰
- 園區網絡架構與技術
- LwIP應用開發實戰指南:基于STM32
- Laravel Application Development Cookbook