(Re)Building a large scale payments system on Rails
summary
Claims that Rails can run large‑scale payments if core problems get fixed and shows concrete experiments: use protected access gem to hide ActiveRecord from general code, add insert-only immutable rows and DB triggers for auditability on MySQL, adopt an explicit parameter validation DSL to fail fast, structure logic as service objects, apply ABC complexity limits, and publish changes via Kafka for downstream consumers. Prototypes run at Airbnb scale but work remains experimental and operational.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:06Why this talk? Audit Trails Failure Behavior Structural Coupling Testability Readability
- 5:01What changed? Who made the change When did they make the change On behalf of whom?
- 27:38Every piece of knowledge must have a single unambiguous authoritative representation within a system.
related talks
22mNitty Gritty Service Building
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
34mToo Big to Fail
27mScaling Ruby Applications: Challenges, Solutions and Best Practices
31mMega Rails
35mTales from the Crypt
39mExploring Rails anti-patterns
35mRails vs. Object Oriented Design