For some things fine, or at least you can sorta get away with it. But in scenarios where you want/need to avoid service interruptions that's not good. The basi

For some things fine, or at least you can sorta get away with it. But in scenarios where you want/need to avoid service interruptions that's not good. The basic scenario is when you have an instance of your service you want to shut down for whatever reason (maintenance, update): (1) start a new instance of your service; (2) route requests to the new instance; (3) shutdown the old instance. In (3) you'd prefer not to just kill any requests in-progress. It's also nice to flush write-buffers (can be used for high-write-frequency but not critical data -- perhaps stats collection or other informational data). I'd definitely keep shutdown simple, but you don't need to go without.