Serverless - The Problem Reactive Was Looking For
summary
Argues that serverless creates the exact constraints reactive patterns solve and shows Lightbend’s Kalix running as a reactive serverless platform. Demonstrates a TypeScript gRPC entity using event-sourced entities that emits checked‑in events, a view service built with generated code and an SQL‑like query, packaged to Docker and deployed; the assets‑by‑location view backfills from the event stream with no migration. Mentions CRDTs, multiple state models, edge replication and that gRPC/TypeScript/Java/Scala are supported.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:07Reactive systems history
- 6:28Reactive Manifesto explained
- 8:12Early reactive adopters
- 9:37Cloud native and reactive
- 11:25Serverless challenges
- 13:10Serverless 2.0 and reactive
- 19:38Calyx as Serverless 2.0
- 21:01Live demo: Calyx features
- 31:22Summary
related talks
28m8 Keys for Successful Serverless Architectures
01h 00mMicroservices and Serverless
49mServerless Event-Driven Services for Spring Developers
28mServerless - the way microservices should be
24mServerless or Servicefull
55mLive Serverless
44mJava: From Stateless-Serverful to Stateful-Serverless
58mServerless - the brief past, the bewildering present, and the beautiful (?) future