Skip to main content
JS Party

Nine pillars of great Node apps

64 min episode · 2 min read
·

Episode

64 min

Read time

2 min

AI-Generated Summary

Key Takeaways

  • Event Loop Management: Monitor event loop utilization percentage and heap used versus heap total metrics rather than RSS memory to identify performance bottlenecks before they crash production systems.
  • Dependency Risk Mitigation: Avoid modules like the deprecated request library (still downloaded 70 million times weekly) and evaluate maintainer activity, bus factor, and long-term viability before adoption.
  • Production Environment Variables: Set NODE_ENV to production in all deployed environments including staging to ensure consistent library behavior, as many packages react differently to this specific variable.
  • LTS Version Strategy: Use Node.js Long Term Support versions in production for 18-month active support plus additional maintenance, avoiding current versions that only receive 6-7 months support.
  • Error Handling Implementation: Implement graceful shutdown patterns using modules like close-with-grace to stop accepting new connections, process in-flight requests, then exit cleanly when errors occur.

What It Covers

Mateo Collina and Natalia Venditto present nine essential pillars for building enterprise-ready Node.js applications, covering event loop management, dependency strategies, monitoring, and production best practices.

Key Questions Answered

  • Event Loop Management: Monitor event loop utilization percentage and heap used versus heap total metrics rather than RSS memory to identify performance bottlenecks before they crash production systems.
  • Dependency Risk Mitigation: Avoid modules like the deprecated request library (still downloaded 70 million times weekly) and evaluate maintainer activity, bus factor, and long-term viability before adoption.
  • Production Environment Variables: Set NODE_ENV to production in all deployed environments including staging to ensure consistent library behavior, as many packages react differently to this specific variable.
  • LTS Version Strategy: Use Node.js Long Term Support versions in production for 18-month active support plus additional maintenance, avoiding current versions that only receive 6-7 months support.
  • Error Handling Implementation: Implement graceful shutdown patterns using modules like close-with-grace to stop accepting new connections, process in-flight requests, then exit cleanly when errors occur.

Notable Moment

Collina reveals that setting NODE_ENV to staging breaks applications because libraries expect either development or production values, creating a language barrier between operations and development teams.

Know someone who'd find this useful?

You just read a 3-minute summary of a 61-minute episode.

Get JS Party summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from JS Party

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

You're clearly into JS Party.

Every Monday, we deliver AI summaries of the latest episodes from JS Party and 192+ other podcasts. Free for up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime