Your HTTP endpoints are data, as well!
summary
Models HTTP endpoints as immutable data values and uses Scala + tapir to define concrete endpoints (add book, list books with optional year and limit filters) rather than annotations. Implements server logic returning Either errors or success wrapped in Future, generates Akka HTTP routes from endpoint descriptions, and emits an OpenAPI/Swagger UI YAML doc. Demonstrates extracting common pieces (base endpoint, limit param), compiles and runs after a path tweak, and the demo works end to end.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:20Welcome
- 6:50Data Structures
- 9:05Demo
- 9:54Endpoint structure
- 15:40Implementation
- 22:50Testing
- 28:44Functional Programming
related talks
52mFrom annotations to code: describing HTTP endpoints with Tapir
49mBeautiful APIs with Scala, Scalatra, Swagger, and Akka
41mHow to write microservices in Scala without Akka
23mOBJECT ALGEBRAS AND WHY YOU WON'T TOUCH HTTP LIBRARY EVER AGAIN
43mAPI first with Swagger and Scala
28mAutomating API Busywork with Scala
36mScale By The Bay 2018 Unconference: Devon Stewart
01h 39mLet’s have some Effective REST