Idiomatic Error Handling in Scala

Error handling in Scala can just be written like Java. Put in a little bit of pattern matching magic and you are done. However, given a little use of Scala built-in terrific beauties it can be made much better. Let us have a look.

Let us look at a quick example

So we have a method called sayHello which misbehaves when you do not pass a string to it. If you call it without a string, it blows up and hence the letMeSayHello invocation blows up as well.

Ok, now traditionally we have been so used to try catch blocks that we put them around.

Ok, so far so good. So we can really write Java in Scala πŸ˜‰

Now let us see a better way (Idiomatic way!) of handling this

Scala comes with something called a Try. The Try type represents a computation that may either result in an exception, or return a successfully computed value. It’s similar to, but semantically different from the scala.util.Either type. Instances of Try[T], are either an instance of scala.util.Success[T] or scala.util.Failure[T].

Interesting, let us see how our code changes now

So, we put a Try block around out sayHello method code. Now the method, letMeSayHello does not need to do explicit error handling. It gets back either Success(“Hello”) or Failure(java.lang.Exception: Huh!)

In the above scenario, it would get Failure(java.lang.Exception: Huh!) and you would be able to extract the value with

Now, there are various ways of dealing with this. You could pattern match on the boolean and take an action like

OR you could simply do a getOrElse

OR you could let the letMeSayHello method handle the success and failure

OR you could get even fancier ! I like this one. The awesome recover mechanism

The recover allows you to recover in case of failures with an alternate condition that you would want to execute which results in a success. Hence, in this case, we mentioned that either we would get a success by default or we would convert the error into a success scenario by writing a recover block so that we can confidently call letMeSayHello.get

You can find the gist here, on the Knoldus GitHub account. Have fun!

Written by 

Vikas is the CEO and Co-Founder of Knoldus Inc. Knoldus does niche Reactive and Big Data product development on Scala, Spark, and Functional Java. Knoldus has a strong focus on software craftsmanship which ensures high-quality software development. It partners with the best in the industry like Lightbend (Scala Ecosystem), Databricks (Spark Ecosystem), Confluent (Kafka) and Datastax (Cassandra). Vikas has been working in the cutting edge tech industry for 20+ years. He was an ardent fan of Java with multiple high load enterprise systems to boast of till he met Scala. His current passions include utilizing the power of Scala, Akka and Play to make Reactive and Big Data systems for niche startups and enterprises who would like to change the way software is developed. To know more, send a mail to hello@knoldus.com or visit www.knoldus.com

5 thoughts on “Idiomatic Error Handling in Scala

  1. Sorry, but nothing about this is idiomatic scala. At a minimum, sayHello should be defined as sayHello(any: String) so that passing in the wrong type is a compile time error. Idiomatic Scala leverages the type system as much as possible such that run time errors like the one above are detected at compile time.

    1. That is fair, you can replace the method to be str:String. The idioms in a language more specifically in Scala is not limited to using the type system. Use of a notable feature in a specific progamming language would constitute an idiom. In this scenario the way Try is used along with benefits that comes along with using it in for comprehensions, filters etc would constitue the Scala idiom. Keep tuned for further treatment of Try

  2. For something like that you should just make your method look like this: def sayHello(any: Any): Either[String, String] = …

    Mostly because throwing exceptions and then immediately catching them isn’t idiomatic Scala at all and you can easily pattern match on the Left and Right subtypes of Either just as much.

    1. > Mostly because throwing exceptions and then immediately catching them isn’t idiomatic Scala at all

      πŸ™‚ Agreed. The intent here is not to show that you throw and catch exception immediately. Replace the {throw Exception} with any processing logic which might result in an exception

    2. The problem I’ve had isn’t when your ONLY using scala, its when you couple it with exception loving java. That’s why this pattern was really helpful for me. Thanks OP!

Leave a Reply

%d bloggers like this: