3 ms·
> This section throws a few numbers out: it claims the UK Bacs system does 580,000,000 transactions a month, or about 223 transactions per second. Curiously it
by Terretta 7y ago
> This section throws a few numbers out: it claims the UK Bacs system does 580,000,000 transactions a month, or about 223 transactions per second.
Curiously it claims Libra can’t do this, but posts no numbers about Libra’s throughtput. Libra’s throughput target is 1,000 transactions/sec (see Section 8: Performance in the Libra paper) with 10 second latencies on consensus time.
OK but 1,000 transactions/sec is a non-starter. A single large seller or popular event driving a live transaction burst can need thousands. Even two decades ago, a WWE event could need 15K sales per second, or 5K per second for Amazon’s black Friday.
If you’re looking to compete with the order of magnitude of a Visa/MC, you’re needing 15,000 - 25,000 per second.
For a commercially available ‘distributed ledger’ able to handle these characteristics (including service level objectives for operating it in production), take a look at the AWS QLDB we asked AWS to make available a couple years ago.
AWS introduced “managed blockchain” and the very different “QLDB” in the same keynote.
Compare under the covers to see why, despite the hype, they introduced QLDB, which is designed for real work when you know who is running the servers:
https://aws.amazon.com/managed-blockchain/ https://aws.amazon.com/managed-blockchain/
https://aws.amazon.com/qldb/ https://aws.amazon.com/qldb/
If you’re a trusted entity or a trusted consortium with legal paper among your members, you probably don’t want the blockchains, you probably want QLDB.