Either Types as an alternative to throwing exceptions in Kotlin
By: Mario Fernández
Tags: Exception, Functional Programming, Kotlin, Arrow, Either

Many of the REST APIs I’ve built lately follow the same pattern. A dumb controller calls a service, which in turn calls a 3rd party API. Simple, well tested, and tidy. Everybody is happy. And then, you start dealing with error conditions.

If we don’t handle the exception, it will bubble up until our API returns a 500 to the caller. As a state-of-the-art backend, we can’t afford this. We have to do something.

Handling failure

A typical pattern in the SpringBoot ecosystem is using an exception handler. You put this method in the controller, and it catches automagically exceptions that happen in the chain. Our caller then gets the error formatted the way we want.

Do not want

I don’t like this way of dealing with error conditions. Error conditions are not something to hide. They happen all the time. They are part of the code. This exception business makes the code difficult to understand. Half of the flow is happening in a way that is partially hidden and easy to miss. It makes the code harder to read.

Instead, I want to show how to make errors explicit by using Either Types.

An example based on JWT

Let’s say that our Service from the diagram above is going to verify JSON Web Tokens. The idea is simple. We are getting a JWT as a string, and we want to know if it is a valid token. If so, we want to get certain properties that we will wrap in a TokenAuthentication . This interface defines it:

Forged signatures

I am using auth0’s library to verify tokens. It has a JWTVerifier class, which receives the encoded token and returns a DecodedJWT . If something goes wrong, it throws a JWTVerificationException . There are different reasons for that, such as an expired token, or an invalid signature.

Kotlin does not have checked exceptions for a good reason. As a consequence, however, the signature is lying to us! This method might throw an exception. Only looking at the implementation will reveal the treachery. As I mentioned, the code becomes harder to read. More context is needed to understand how the app behaves.

The explicit approach

There are two things I want to change in the Verifier implementation.

The verify method should not throw an exception. The signature of the method should reflect that an error might happen.

A naive approach would be to use a nullable type. verify would return TokenAuthentication? . But it has a fatal flaw: We are losing all the context about what actually went wrong. If there are different causes for the error, we want to keep that information. Enter Either (dum dum dum...).

The Either datatype

Originating from the functional community, Either is a class whose value can be of two different types, called left and right. By convention, Right is for the success case and Left for the error one.

It is essentially an option type that keeps the information about the error in it. Just what we need! You can implement it yourself, but I’m going to use the excellent arrow library, which includes an Either type, among many other functional goodies.

With that being said, let’s rewrite our code to make use of Either .

Adapting the interface

The Verifier class returns an Either type to indicate that the computation might fail.

Note that we are still using the exception to signal an error, but we are not throwing it anymore.

Wrapping the code that throws

Inside our implementation of Verifier , we are wrapping the problematic code from the library that we use with an extension method called unsafeVerify :

Arrow provides a ton of convenience methods to make it simpler to use. Thanks to the left and right extension methods, this code is quite tight.

Using it as a client

Implementation is done. How do we use this in our code? Whenever you want to operate on the underlying type, ignoring the error case, you can use map . That allows you to chain calls without having to check whether the value is valid or not. There is an equivalent mapLeft for the error side.

verifier

.unsafeVerify(jwt)

.map { it.asToken() }

Ultimately, you want to convert the Left and Right branches into one value. One option is to use the functional fold method.

Or we can use a when expression because Left and Right happen to be sealed classes.

So that’s pretty much it. The Verifier doesn't throw exceptions anymore. Instead, an Either wrapping the token is returned, with additional information about the error in case something goes wrong. We can manipulate the result throughout our application. When we are ready to unwrap the value, we use one of the two methods above to convert it to one value. In our case, the success case returns a 200, and the error a 502. To see the full implementation, check this.

Appendix: A built-in solution

Since Kotlin 1.3, there is a built-in way of dealing with computations that can fail. It is the Result class, which is typically used in a runCatching block:

This class can’t be used as a return type yet, so we can’t use it for our interface. Moreover, Either integrates with all the other arrow library. I plan to write in more detail about other things that you can do with it, such as converting it to an Option or chaining multiple calls in more complex examples.

Conclusion

Either is a great way to make the error handling in your code more explicit. I've been trying to make all my services return it if there are failure conditions. The controller is then responsible for branching based on success/error and deciding what to do.

I think that the code is a lot clearer this way, and worth trying. It’s one step towards more functional code. I’ll follow up with others, including other parts of arrow, which I like quite a bit.