> Their blog post about how to rewrite QLDB apps to use Aurora PostgreSQL instead
Straight callback to all the "you don't need a blockchain, you just need a database".
Straight callback to all the "you don't need a blockchain, you just need a database".
QLDB is an immutable database with allowing you to move back and forward in history and do live streaming of events etc with cryptographic verification built in.
You _can_ set up Postgres like this but it's a lot of hoops and not very user friendly (some monstrosity involving DMS, Kinesis Firehose and what not).
Which no one ever needed.
It's just increases scope x100 to get anything done, so few do it... but if the tooling was available, almost all stateful applications would benefit from it.
The tooling just doesn't exist. Doing it with half-assed tooling increases the scope of literally every development you'd be doing, so nobody bothers with it. Ive never worked with this particular database, so no idea how it would work in practice here.
Having an immutable database that was able to track fraud ratings, along with when exactly it occurred with the data available at the time was pretty cool. You could probably do it with other tools, but having it all in one product was nice.
The cryptographic verification was helpful for legal defence. I can't think of any other uses so we may have been their only customers.
QLDB is the 'blockchain' businesses need. If you think of blockchain design choices as a set of dip switches, QLDB is the only one with all the correct settings for distributed business transaction value at scale.