Easy scala functional-programming

Why do search and data platforms like Zalando's use Scala?

The 30 second answer

Zalando's tech radar lists Scala in Adopt next to Java and Kotlin, and its search team's Elasticsearch migration post is tagged Scala and Java. The draw is that Scala makes immutable data the default, models work as transformations over collections and streams, and pairs with actor libraries like Akka for concurrency without hand-written locks. For a service handling many requests over large catalogs, that means fewer shared-state bugs.

What the public record shows. Zalando's open-source tech radar (edition 2026.05) places Scala in the Adopt ring with Java, Kotlin and JavaScript. Zalando Engineering has Scala and Akka posts going back years, including back-pressure for a sharded Akka cluster (2019) and a distributed cache built with Akka on Kubernetes (2018). The Search & Browse department's 2023 post on migrating Elasticsearch 7.17 to 8.x is tagged Scala, Java and Backend. That is evidence the language is used; it doesn't say which exact service uses which language, so don't claim more in an interview.

Why the language fits this kind of work.

  • Immutability by default. The Scala 3 book says to always declare a variable with val (like final in Java) unless you need var, and the collections guide says Scala always picks immutable collections by default. A Java developer has to opt in to immutability; a Scala developer has to opt out.
  • Transformations instead of shared state. Search and indexing are mostly pipelines: read documents, filter, map, enrich, group, write. Scala's collections and streaming libraries make that the natural style, so data moves through steps instead of being edited in place.
  • Actors for concurrency. Akka (and its Apache fork, Pekko) implement the actor model. The Akka docs say actors free the developer from explicit locking and thread management, because each actor processes one message at a time.

How to say it in an interview. "Scala nudges the team toward immutable data and pipelines, which is a good fit for search and indexing services. I write Java the same way where I can: records, unmodifiable collections, streams, and single-owner state."

Sources (7)
  1. Zalando Tech Radar (edition 2026.05): Scala in Adoptopensource.zalando.com
  2. Zalando Engineering: Migrating from Elasticsearch 7.17 to 8.x (2023), tagged Scala and Javaengineering.zalando.com
  3. Zalando Engineering: Back-pressure strategy for a sharded Akka cluster (2019)engineering.zalando.com
  4. Zalando Engineering: Distributed cache with Akka on Kubernetes (2018)engineering.zalando.com
  5. Scala 3 book: variables and data types (val versus var)docs.scala-lang.org
  6. Scala collections overview: immutable collections are the defaultdocs.scala-lang.org
  7. Akka docs: Introduction to actorsdoc.akka.io