How Booking.com cut Node.js costs by 38% with Watt

Adventures in Nodeland · 1 week ago · 27

Booking.com reconfigured a large-scale Node.js rendering service using Watt instead of pm2 clustering. It cut computing costs by 38% after using 30% fewer pods and reducing per-pod memory by 20%, with latency improvements up to 10% at p75/p99/p99.9. The service now uses Watt worker threads with kernel-level connection handling and Watt’s thread monitoring/restart behavior, enabling higher request capacity under load.