Taking Elixir Live at a Bank
summary
OP Labs ships a production biometric payment system called Pivo Kasvomaksu used in Finnish coffee shops, built as two Elixir services (each ~10,000 lines of Elixir) plus Go for 2D image work, integrating multiple facial recognition providers and POS/tablet/mobile clients. Requirements force a <3s pipeline, PSD2 compliance and liveliness checks; the system runs in production ~1.5 years with no full crashes, scales to thousands of terminals and tested ~150 tx/s, passed a third‑party security audit, and surfaced practical issues: circular deps, large GenServer refactors and Phoenix synchronization challenges.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:24Banking differences
- 5:20Typical large banking architectures
- 7:14Face Payments
- 9:03Elixir anyone?
- 13:22What are you drinking?
- 16:50What you think the world looks like
- 19:20How to kill a thread in Java?
- 20:13How to kill a process in Elixir
- 21:53Sequential code is simple code
- 25:49Requirements: achieved
- 27:18Microservices
- 29:13Security & IPR Audit
- 30:03Problems
- 32:47Practical architecture advice
- 33:55New developers learning Elixir...
- 35:29Adopting Elixir in a large organization
related talks
47mElixir for curing product development pains
36mReal-time card payments in Erlang
47mElixir for curing product development pains?
27mHow Elixir is driving Australian product innovation
01h 01mArchitecture Decisions: A Case Study -
32mEnhancing Security, Reliability, and Global Scalability in FinTech
41mRewriting critical software in Elixir - a case study
49mKeynote: How to sell Elixir (Again)