Hacker News new | ask | show | jobs
by m3kw9 2762 days ago
If centralized, why not just restrict the API to make history immutable? Lol
2 comments

When the largest cloud provider takes time to create and market a new product it's probably worth thinking about for more than a "lol".
AWS employee here. QLDB has been used internally at AWS for quite some time. We decided to turn our internal service into an external facing product because we saw a demand for a ledger system with central authority. Many people were trying to force Blockchain to accomplish this, while we already had an internal ledger solution that is far more scalable while still being cryptographically verifiable.
What's it used for? (Can you say?)
A lot of stuff. See the two tweets I referenced in this reply: https://news.ycombinator.com/item?id=18553937
Thank you!
This I’m that’s why I’m asking
That doesn't give you the ability to cryptographically verify integrity of the database. Think git repository with pgp signature on every commit.
I think once centralized, there is inherently something wrong with blockchains. There is always chance of bait and switch, even though you trust amazon.
Sure but QLDB isn't a blockchain. Blockchain is just one of many things that can be implemented on top of it. You could implement the same thing with an SQL database and signed history tables.
QLDB != Blockchain. It does not use blockchain at all.