Less than 18 months ago, QLDB had zero developers and zero lines of code - just a Press Release and an FAQ. Today, we have a GA service! It has been an amazing ride, and thanks to all the people who came together to make it possible! Ask me anything!https://aws.amazon.com/blogs/aws/now-available-amazon-quantum-ledger-database-qldb/ …
I’d be most interested to hear what the “close but no” use cases are. E.g. if you need a ledger but it has to do X, it isn’t a good fit.
-
-
The main thing is that if you need multiple parties to agree that a transaction is valid, QLDB is not for you. Think of database controls versus Hyperledger Fabric chain code. E.g. in Fabric, you can have code that runs that says update this key to this value, but only if it's
-
signed by X. Or only if the resulting balance won't go negative. And then some set of parties have to agree to install that code, and then some set have to agree that the constraints are met before updating the state. In QLDB, you can have PartiQL statements that say
- 2 more replies
New conversation -
-
-
My guesses: Access controls! They aren't mentioned anywhere and would be really hard to do and have hash-block verification. Sometimes, your actually need to really delete something.
-
We have plans for both of those, but they aren't in the GA product.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.