Scala with Bazel
summary
Three companies report concrete Bazel Scala migrations: Wix automatically converts ~200,000 lines of Maven modules into 1,500 Bazel targets, yields ~90% developer build-time reduction on local machines, and ships a synchronizer that propagates org-wide dependency changes to WORKSPACE/third_party. Databricks runs a monorepo with ~500k Scala lines, builds ~900 Scala targets and ~2,000 test targets using an SBT→Bazel converter to keep parallel SBT/Bazel builds during migration. Stripe runs a ~200k-line repo, sees large gains from Bazel workers and mostly reproducible builds with two remaining LLVM-like compiler/workspace bugs.
AI-written summary · about
chapters (17)
- 0:00Scala with Bazel intro
- 1:48Wix Maven to Bazel
- 6:03JVM interoperability in Scala
- 8:33Testing Scala libraries
- 9:57Strict Scala dependencies
- 12:26Data Bricks' Bazel setup
- 14:11SBT migration challenges
- 18:06SBT to Bazel conversion
- 20:33Bazel benefits at Data Bricks
- 22:16Stripe's Scala build journey
- 24:23Evaluating Bazel at Stripe
- 25:44Bazel reproducibility & parallelism
- 27:50Bazel pain points
- 31:43External dependencies & Maven
- 33:10Bazel APIs & stability
- 35:39Scala type system challenges
- 36:43Bazel future at Stripe
