3 ms·
The double-bookkeeping Twilio is using -- what's the downside to it? Is it only updated per-minute with Redis doing the second-to-second usage and then rolled o
by Xorlev 13y ago
The double-bookkeeping Twilio is using -- what's the downside to it? Is it only updated per-minute with Redis doing the second-to-second usage and then rolled off into MySQL?
I'm curious how that's working, if you don't mind the question.
- RobSpectre 13y agoI'm not sure there is a "downside" to be had - it is an important requirement to every billing solution of any scale at all. The term is borrowed from accounting (http://en.wikipedia.org/wiki/Double-entry_bookkeeping_system http://en.wikipedia.org/wiki/Double-entry_bookkeeping_system) and states that each transaction gets recorded in a different ledger. Our implementation at Twilio divides the two in stages of the transaction lifecycle that we allude to in the OP - in-memory for in-flight (when a call or SMS message is initiated) and disk for post-flight (when a call or SMS message is complete).