官术网_书友最值得收藏!

Chapter 2. Node.js Essential Patterns

Embracing the asynchronous nature of Node.js is not trivial at all, especially if coming from a language such as PHP where it is not usual to deal with asynchronous code.

In synchronous programming, we are used to the concept of imagining code as a series of consecutive computing steps defined to solve a specific problem. Every operation is blocking, which means that only when an operation is completed is it possible to execute the next one. This approach makes the code easy to understand and debug.

Instead, in asynchronous programming, some operations, such as reading a file or performing a network request, can be executed as an operation in the background. When an asynchronous operation is invoked, the next one is executed immediately, even if the previous operation has not finished yet. The operations pending in the background can complete at any time, and the whole application should be programmed to react in the proper way when an asynchronous call finishes.

While this non-blocking approach could almost always guarantee superior performance compared to an always-blocking scenario, it provides a paradigm that could be hard to reason about and that can get really cumbersome when dealing with more advanced applications that require complex control flows.

Node.js offers a series of tools and design patterns to deal optimally with asynchronous code. It's important to learn how to use them to gain confidence and write applications that are both performant and easy to understand and debug.

In this chapter, we will see two of the most important asynchronous patterns: callback and event emitter.

主站蜘蛛池模板: 尉氏县| 九寨沟县| 顺平县| 卫辉市| 阿拉善盟| 金塔县| 广东省| 彰武县| 温泉县| 连江县| 日土县| 淮安市| 榕江县| 蒲江县| 公主岭市| 中牟县| 沐川县| 汉川市| 永宁县| 宽城| 闻喜县| 集贤县| 塔城市| 山阴县| 石林| 商丘市| 榆树市| 佳木斯市| 历史| 育儿| 邛崃市| 永泰县| 高陵县| 黔江区| 高台县| 蒙阴县| 石泉县| 西和县| 中阳县| 额济纳旗| 靖安县|