Faster Delivery with Pedestal and Vase
summary
Pedestal provides an interceptor chain architecture where every handler is a map-in-map-out function inside a context map, routing can hit 60 nanoseconds on the presenter’s laptop, and platform bindings span servlet, Kafka and AWS Lambda. Vase sits on Pedestal and makes services declarative data-driven microservices: descriptors, action literals (interceptors), Datomic transactions, and clojure.spec validation turn weeks of plumbing into minutes — a microblog installs in under five minutes — enabling disposable inventory services that actually work.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:10Best Sustainable Competitive Advantage
- 2:24More with Less
- 4:36Goals
- 5:22New website
- 5:47What is Pedestal
- 7:55Pedestal Service
- 10:10The Interceptor Chain
- 13:29The Chain Provider
- 15:05Pedestal Route
- 17:00Antifragile
- 18:35Vase
- 19:42Microblog Service
- 20:06Service Descriptor
- 20:35Vase Norms
- 21:46Data Validation
- 22:51Vase API
- 33:55Summary
related talks
38mUnlocking data-driven systems
33mMicroservices with Vase and Linkerd
28mPractical Microservices, Practical Whiskey
46mSubatomic, Supersonic, Reactive
41mHelping voters with Pedestal, Datomic, Om and core.async
41mBuilding Low Latency Microservices & Monoliths in Java
40mHow to Build Ultra-fast Java Microservices. Overcome Pitfalls of Data Persistence
41mThe Slideless Microservices Session