On 7/13/18 3:53 PM, Paolo Invernizzi wrote:
On Friday, 13 July 2018 at 13:15:39 UTC, Steven Schveighoffer wrote:
On 7/13/18 8:55 AM, Adam D. Ruppe wrote:
On Wednesday, 11 July 2018 at 12:45:40 UTC, crimaniak wrote:
This error handling policy makes D not applicable for creating WEB
applications and generally long-running services.
You use process isolation so it is easy to restart part of it without
disrupting others. Then it can crash without bringing the system
down. This is doable with segfaults and range errors, same as with
exceptions.
This is one of the most important systems engineering principles:
expect failure from any part, but keep the system as a whole running
anyway.
But it doesn't scale if you use OS processes, it's too heavyweight. Of
course, it depends on the application. If you only need 100 concurrent
connections, processes might be OK.
Came on, Steve... 100 concurrent connections?
Huh? What'd I say?
-Steve