Microservices on Unison Cloud: Statically Typed, Dynamically Deployed
summary
Unison Cloud sends and runs function-level code addressed by a 512‑bit content hash so there are no builds or containers: deployment is literally a function call that includes the full transitive dependency hashes. Services are statically typed (effects prevent unauthorized IO) and can be called by hash or by a typed name; the platform does adaptive service graph compression to co‑locate hot callers and eliminate network hops. Demo: an ECB‑backed currency converter plus a 24‑hour demon for rate refreshes deploys, serves HTML, scales automatically and is garbage‑collected when idle.
AI-written summary · about
chapters (10)
- 0:00Unison and Unison Cloud intro
- 1:51Traditional microservices pain
- 3:43Unison for distributed programming
- 12:13No builds or containers
- 16:29Deploy with one function
- 22:03Safe typed service calls
- 27:50Adaptive graph compression
- 30:39Running periodic tasks
- 37:26Live currency converter demo
- 38:29Q&A
related talks
31mTyped and compositional microservices in Unison
41mIntroduction to the Unison programming language
22mProgramming the worldwide elastic supercomputer with Unison
01h 04mHighway to Heaven – Building Microservices in the Cloud
34mCloud Chaos and Microservices Mayhem
23mMicroservices – Sean Smith
25mTES Microservices
52mMicroservices & the Inverse Conway Maneuvre