Scala Ecosystems: Lightbend vs Typelevel
summary
Compares Scala ecosystems by showing how Lightbend stacks (Play, Akka, Slick) use Futures and Akka Streams so HTTP clients return Future[Source] and composition runs eagerly, while Typelevel stacks (Cats Effect, fs2, Doobie) use IO/AYO descriptions so effects are lazy and parallelism is explicit. Demonstrates merging two keyword streams implemented both with Play+Akka and with sttp+fs2 producing the same output, shows Slick needs manual mapping whereas Doobie generates mappings at compile time, and recommends migrating from Futures to IO as a practical first step.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:44Pure functions: definition
- 3:16Pure functions: advantages
- 4:07Effects Definition
- 5:56Future: examples
- 7:1610: examples
- 8:58Type classes Ad hoc polymorphism
- 20:51Conclusion: Strengths
related talks
39mThe Futures are Calling and I Must Choose
34mFunctional Programming: The Enterprise Edition
46mIntegration of Distributed Real-time Data Computing in a Web App
31mSCALA FROM B TO F - BACKEND DEVELOPER ON FRONTEND
31mHow I learned to stop worrying and love the frontend
55mClosing Keynote
33mJourney to the Heart of the For-Yield
52mGo Fully Functional and Take Your Legacy Code with You!