Node.js Underground Rail Event: UI Rendering, Java Migration & Fiber Debate

Preface

There are two ways to acquire knowledge: learning theory and practicing it. Both are essential. While theory is important, the ultimate goal is to combine theory with practice to achieve learning‑by‑doing and using practice to promote learning. Node.js has been developing for nearly eight years since 2009. The community ecosystem has grown from a modest beginning to a large, mature ecosystem that enables impressive online applications for enterprises.

In March, the Node.js Underground Rail held its fourth event focused on deep practice, gathering in the historic city of Nanjing. With respect and honesty, two popular speakers and several guests shared experiences and lessons from applying Node.js in practice.

Review

Node.js Component UI Rendering

To let search engines index your site, server‑side rendering (SSR) is indispensable. SSR also improves site performance because the browser can render the page before loading JavaScript. Yuan Yan from Taobao introduced a React‑based component UI rendering solution on the Node side, addressing the low first‑screen performance and weak SEO of traditional SPA applications, and discussed the pros and cons of conventional template rendering.

Java Migration to Node.js – Practical Sharing

Yi Cai from Taobao presented a case study of migrating a micro‑poster project from Java to Node.js, sharing experiences from architecture design, technology selection, data, services, and UI migration, as well as before‑and‑after performance comparisons. The talk summarized key migration points and Node.js enterprise‑level development guidelines.

Locating Online Node Runtime Errors

Under Node.js’s single‑process model, robustness can be backed up by tools like PM2, but sporadic online errors remain hard to pinpoint, leading to vague bottleneck locations and low investigation efficiency. Huang Yijun shared a practice of building a low‑level monitoring system based on the V8 engine to quickly locate abnormal points in online processes.

From Flint to Aircraft Carrier – Four Refactors of the Fiber Engine

Although it may look like advertising, the presenter repeatedly emphasized that it was not. The PPT repeatedly displayed the “Third Pole” logo, revealing its nature. Nonetheless, Fib.js is an excellent library that combines V8 fibers to solve callback hell and provide stronger concurrency. This talk shared the refactoring ideas and experiences of Fib.js to inspire new thinking.

Debate: Which Asynchronous Solution Is Better?

After the presentations, the host sparked a debate—the most interesting part of the Node.js Underground Rail. The “Pro” team, consisting of Han Quan, Yuan Yan, Yi Cai, and Huang Yijun, argued that the newly added async/await solution is superior. The “Con” team, represented by Wang Aike, Xiang Ma, Shen Zhimin, and Zhuang Shaowei, advocated that fiber offers a better asynchronous solution.

The debate quickly turned heated, with both sides exchanging arguments based on theory, practice, and industry solutions. The audience enjoyed the lively exchange, and after a time‑limit vote, the “Con” side led by Xiang Ma won, claiming “fiber is better for asynchronous solutions.” The outcome remains open for further discussion, as scientific progress relies on continual correction and refinement.

During the award ceremony, the winning team appeared visibly happy. Whether it was “friendship first” or an unexpected twist, the size of the prize in the guests’ hands hinted at the story.

Conclusion

This brief yet intensive gathering allowed participants to learn from industry leaders, contribute to the evolution of technology, and gain references for future business challenges. Thanks to all attendees; we look forward to the next meeting!

Below are photos from the event. As the organizer, I was initially shy, and many participants avoided the camera, but after a few attempts the atmosphere became as lively as during the debate.

For those who missed the sharing, the Node.js Underground Rail materials, including videos and PPT links, are available via the original article.