Scaling Scala
summary
Spotify uses Scio on Apache Beam and Google Cloud Dataflow to run thousands of Scala pipelines in production, currently about 11,000 unique pipelines with ~60,000 executions/day processing petabytes and roughly 800 billion events/day. The stack yields strong static typing, macro-derived BigQuery/parquet/Avro mappings and compile-time coder derivation, but faces pain points: closure serialization bugs in distributed runs, cross-publishing for Scala 2.12/2.13, dependency conflicts, and a slow, costly migration path to Scala 3 mitigated by a mono-repo and a custom sbt plugin.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:21Finance Insights
- 12:09Why Scala
- 15:20Compiler
- 17:41Data Processing
- 22:47Data Engineering Training Internally at Spotify
- 23:03Train Data Engineers To Do Data Engineering
- 23:29The Golden Pass
- 24:06Tech Universities
- 26:30Civilization Issue
- 28:01Binary Compats
- 28:43Migrating to a New Version of Scala
- 30:19Dependency Conflict
- 32:44Svg Plugin
- 36:58Should We Migrate








