Skip to main content
Version: 2.x

Three Types of Errors

We should consider three types of errors when writing ZIO applications:

  1. Failures are expected errors. We use ZIO.fail to model failures. As they are expected, we know how to handle them. We should handle these errors and prevent them from propagating throughout the call stack.
  2. Defects are unexpected errors. We use ZIO.die to model a defect. As they are not expected, we need to propagate them through the application stack, until in the upper layers one of the following situations happens:
    • In one of the upper layers, it makes sense to expect these errors. So we will convert them to failure, and then they can be handled.
    • None of the upper layers will catch these errors, so it will finally crash the whole application.
  3. Fatals are catastrophic unexpected errors. When they occur we should kill the application immediately without propagating the error furthermore. At most, we might need to log the error and print its call stack.

ZIO Chat

Hi, fellow coder! ๐ŸŒŸ Welcome to your ZIO adventure with the ZIO Chat Bot. ๐Ÿš€ Let's master functional Scala together. From referential transparency to concurrent prowess, I've got your back. Ready to dive in? Your questions, my insights โ€“ let's conquer ZIO! ๐Ÿ’ก๐Ÿค–