May 2018
Intermediate to advanced
412 pages
9h 3m
English
I’ve said it a few times now: the Elixir way says not to worry much about code that crashes; instead, make sure the overall application keeps running.
This might sound contradictory, but really it is not.
Think of a typical application. If an unhandled error causes an exception to be raised, the application stops. Nothing else gets done until it is restarted. If it’s a server handling multiple requests, they all might be lost.
The issue here is that one error takes the whole application down.
But imagine that instead your application consists of hundreds or thousands of processes, each handling just a small part of a request. If one of those crashes, everything else carries on. You might lose the work it’s doing, ...
Read now
Unlock full access