Stone Bank: how a team of initially 5 (...)
summary
A five-person team builds an open bank API on Elixir, deploys with Kubernetes plus clustered BEAM experiments, and runs core services with Phoenix, Ecto/Postgres and Kafka; they implement a custom triple DES two-key 16-byte cipher to satisfy legacy integrations, avoid long DB transactions by moving external calls out of Ecto.Multi, and add telemetry to find NIF contention in crypto. After two years in production the system authorizes 8.5M actions and sends 2M webhooks/day, with hundreds of thousands of daily transactions and no major stability failures.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:42What is Stone
- 3:17Why Elixir
- 5:23Challenges
- 8:55Old cryptography
- 11:03Kubernetes
- 17:49Lessons learned
- 22:16Hidden NIPS
- 23:25Telemetry
- 25:45Was it worth it
- 28:49Questions
related talks
41mBuilding a Bank (with DDD, Microservices, and Autonomous Teams)
55mFrom the engine to the bridge - building systems that scale
47mElixir for curing product development pains
17mExtreme Engineering-Elements of Building a High -scale Broking Application
45mKeynote: One Monolith, Many Teams: Growing an Org...
34mCrafting the Core - Why and How We Built the Core Banking System
27mSlicing 'Big Elephant' systems into micro-services
45mTaming the FinTech Beast