Menu
I am using the "aws-sdk:^2.576.0" and "amazon-qldb-driver-nodejs:0.1.0-preview.2", and following the node-sdk's sample code for qldb. I am calling the node-sdk functions via the REST APIs exposed.
So for the read table operation, i.e., SELECT * query (scanTable from the sample code), following is the latency breakdown:
I'm getting a new session for every transaction from the session pool using pooledQldbDriver.getSession() and have a decent internet connection of nearly 100mbps.
Is this much latency expected? Am I doing something wrong, and how can it be reduced further?
269
High-performance and highly available: Since QLDB is centralised and doesn't use blockchain technology, it doesn't need peer nodes to validate a transaction before it can store the data in the ledger. Therefore, transactions are easier and faster than on decentralised/blockchain frameworks.
Blockchain allows you to build applications where multiple parties can securely and transparently run transactions and share data without the need for a trusted, central authority whereas, Amazon Quantum Ledger Database (Amazon QLDB) is a fully managed ledger database owned by a central trusted authority that provides ...
Immutable and Transparent This ensures that your stored change history cannot be deleted or modified.
How does Amazon QLDB scale? With Amazon QLDB, you don't have to worry about provisioning capacity or configuring read and write limits. You create a ledger, define your tables, and QLDB automatically scales to support the demands of your application.
(As per the comments in your question.)
Right now you're measuring the latency between India and us-west-2, not the latency of QLDB operations. Please use a region that has lower latency (https://docs.aws.amazon.com/general/latest/gr/qldb.html) or rely on the server-side metrics that you should be able to find in the CloudWatch console.
153
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
