Announcing Akka 24.05: More Security. More Performance. More Efficiency. Watch the Webinar Replay
scala sbt maven gradle intellij compiler

Making Scala Faster: 3 Expert Tips For Busy Development Teams

How To Make Your Scala Applications Compile Faster

View on Slideshare

With Scala, JVM developers get a host of benefits over other programming languages—from code conciseness (fewer LOC) and native scalability to support for functional programming paradigms and type safety, Scala is the language of choice for modern enterprises like Amazon, HPE, PayPal, and Walmart.

Yet Scala also brings something that developers have a hard time accepting: long compile times. We have the most powerful computers ever made at our fingertips, yet we often spend up to an hour or more each day waiting for compilation to finish. It’s not uncommon for a project to experience compilation times of 5-10 minutes or more, and a change to even a single line of code can increase compilation times 10X.

In this special guest webinar with Mirco Dotta, co-founder of Triplequote LLC (the creators of Hydra), we take a deeper look into what affects Scala compilation speed, why a combination of language features, external libraries, and type annotations make compilation times generally unpredictable, and what you can do to speed it up by orders of magnitude. We’ll go through:

  • Understanding some of the most common bottlenecks in Scala builds.
  • Effective use of type class auto-derivation for cutting compilation times.
  • What are some average compilation speeds, and how to know if you have a productivity blocker.
  • BONUS: a 6-7min demo of the Hydra Compiler and Dashboard (after the Q/A) 

Watch The Full Presentation, Q/A, And Demo

Watch on YouTube

More Resources To Enjoy

We're here to make your journey with Scala as fun and productive as possible. Check out these resources to learn, build, and educate your team about Scala:



The Total Economic Impact™
Of Lightbend Akka

  • 139% ROI
  • 50% to 75% faster time-to-market
  • 20x increase in developer throughput
  • <6 months Akka pays for itself