Elixir and money
summary
Argues that Elixir handles money by design: it matches CAP tradeoffs so systems choose availability vs strong consistency deliberately, uses Postgres and Ecto.Multi to batch transactional effects, and relies on client-generated UUIDs plus retry-safe PUT semantics to avoid duplicate transfers. Shows a production case on a single Heroku dyno replacing larger Ruby fleets, uses immutability and supervision trees for failures with the let it crash restart model, and reports that this approach actually works in real billing and direct-debit flows.
AI-written summary · about
chapters (23)
- 0:00Intro
- 2:50Financial Systems
- 8:20Balances
- 9:57Transactions
- 14:41Let it crush philosophy
- 16:42Fresh state
- 18:00Crash philosophy
- 18:35Apollo 11 crash
- 20:38How the system works
- 21:53Two generals problem
- 23:26Clientserver architecture
- 24:01Retry
- 25:43Summary
- 26:19Testing
- 26:58Pipe chain
- 27:54Plug
- 29:52Multi
- 30:47Data structure
- 31:31Reading from database
- 32:20Repo module
- 32:42Other benefits
- 35:12Drawbacks
- 39:22Questions
