In distributed systems engineering, few architectural divides are as deep—or as philosophically opposed—as how different runtimes handle failure. Should the application try desperately to catch the exception, sanitize the state, and limp forward?
In distributed systems engineering, few architectural divides are as deep—or as philosophically opposed—as how different runtimes handle failure.
Should the application try desperately to catch the exception, sanitize the state, and limp forward?
Or should the faulty component instantly self-destruct, leaving a supervisor to spin up a …
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
In distributed systems engineering, few architectural divides are as deep—or as philosophically opposed—as how different runtimes handle failure. Should the application try desperately to catch the exception, sanitize the state, and limp forward? Or should the faulty component instantly self-destruct, leaving a supervisor to spin up a …
When an unexpected error occurs, what should happen?
Open the app view to save this story, compare related coverage, and continue from the same source.