record transaction history.
What do you like best?
If you want to make an application in which many financial transactions are taking place every day. So you must have to manage its ledger (like transaction processed or failed if failed whats the reason etc.). But you manage all of this on your self the task may be a little hard but the main problem is that if you are managing it on your own so your object is mutable which can be edited or altered. But QLDB object ledger history is immutable which can not be edited.
What do you dislike?
I don't dislike anything. But its a serverless technology so you should be a little comfortable with could computing.
Recommendations to others considering the product:
For finance-related applications, you must use it. It's a great serverless database.
What problems are you solving with the product? What benefits have you realized?
I am developing a trading application in which I am using QLDB. Its queries are similar to SQL Database. But its benefit is this when you use it as your database you will get one additional functionality which is it records transactions history of my transaction table its indexes everything which is changed over time and all in an immutable object so can not be altered. If you are developing a finance-related application you must use this.