Insights from Node.js Underground Rail: SSR, Java Migration, Fiber vs Async

Preface

Acquiring knowledge comes from theory and practice; both are essential. While learning theory is important, the ultimate goal is to combine it with practice to achieve learning‑by‑doing and using‑to‑learn. Node.js has evolved for nearly eight years since 2009, growing from a sparse ecosystem to a large community that enables impressive online applications for enterprises.

In March, the Node.js Underground Rail held its fourth event in Nanjing, gathering two popular hosts and several guests to share experiences and summaries of Node.js in practice.

Review

Node.js Component UI Rendering

Server‑side rendering (SSR) is indispensable for search‑engine indexing and can improve site performance by rendering pages before the browser loads JavaScript. Yuan Yan from Taobao introduced a React‑based component UI rendering solution on the Node side, addressing the low first‑page performance and weak SEO of traditional SPA applications and discussing the pros and cons of conventional template rendering.

Java to Node.js Migration Practice

Yi Cai from Taobao shared a case of migrating a micro‑poster system from Java to Node.js, covering architecture design, technology selection, data, services, UI migration, and before‑after performance comparisons. He summarized key migration points and established enterprise‑grade Node.js development guidelines.

Locating Online Node Runtime Errors

Under Node.js’s single‑process model, robustness often relies on tools like PM2, but occasional production errors are hard to pinpoint, leading to vague bottleneck identification and low investigation efficiency. Huang Yijun presented a V8‑engine‑based low‑level monitoring practice that quickly locates runtime exceptions.

From Fire‑Starting to Aircraft Carrier — Four Refactors of the Fiber Engine

Although the talk resembled an advertisement, the presenter emphasized that Fib.js is an excellent library that leverages V8 fibers to solve callback hell and provide stronger concurrency. The session shared refactoring ideas and experiences to inspire new approaches.

Debate: Which Asynchronous Solution Is Better?

After the talks, the host sparked a debate between two teams. The “pro” side (Han Quan, Yuan Yan, Yi Cai, Huang Yijun) advocated the newly added async/await, while the “con” side (Wang Aike, Xiang Ma, Shen Zhimin, Zhuang Shaowei) argued that fiber offers a better solution for asynchronous programming.

The debate became increasingly heated, with each side defending its stance using theory, practice, and industry solutions. Eventually, a time‑limit forced a vote, and the “con” side led by Xiang Ma won, arguing that “fiber is a better solution for asynchronous operations.” The final verdict remains open for further discussion.

During the award ceremony, the winning team appeared visibly happier, raising questions about whether friendship or a mishap determined the outcome.

Conclusion

The meetup was brief yet intensive, allowing participants to learn from experts, contribute to technological evolution, and gain references for future business challenges. Photos and the presentation materials are provided for those who missed the session.