I apologize - "hot code swapping" may be a misnomer. Naught does the process that you describe about taking the resource out of the pool, giving it the new goodies, and booting it up again.

The native cluster API is the Unicorn equivalent in the node.js world. Naught is essentially unicorn for node. And naught is the equivalent of a process supervisor.

Fair point about logrotate. Here's a counter one: The server that you describe requires 4 moving parts: 1. the app code, 2. the unicorn equivalent, 3. a process supervisor, 4. logrotate in a cron job. An app deployed with naught requires 2: 1. the app code, 2. naught.