How to Elm-ify Your ML
summary
Stripe builds a small, principled feature system: a free applicative feature DSL that describes feature logic as an AST, compiles to batch (MapReduce/Scalding/Summingbird) or a Kafka-backed push backend, and enforces time-aware lookups so temporal leakage is impossible. Unit tests run as lazy streams (example: dog bark/jump/howl test). Real-time scoring hits ~10–50 ms for typical graphs. The claim is that separating business logic from execution yields consistent training vs. scoring and simpler, optimizable runtimes.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:52What is machine learning
- 3:06Key challenges
- 6:41Functional programming and time
- 10:35Magickal matrices
- 14:21Scala type classes
- 15:59combinators
- 18:47free implementation
- 22:13map
- 24:01lookup
- 28:30how to run
- 30:55pushbackend
- 31:52conclusion
- 34:20windowing
related talks
10mFast Sub-ML Usecase Development using Feature Stores
17mCreating & operating ML models from event-based data using feature stor...
13mDesigning Feature DSLs: Principles and Tradeoffs
31mLeveraging GraphQL for Continual Learning in Real-Time ML Systems
53mAdventures in Elm: Events, Reproducibility, and Kindness
36mBuild prod ML systems with feature /training /inference pipelines
20mSemblance: Feature Generation In Real-Time and Batch Without Time-Travel
01h 28mFunctional Programming for the Web with Elm
