[kybernetikos]

Because we wanted transactions signed with the key of the transactor and a complete audit history (ideally one that couldn't be tampered with, even by an admin).

By using ethereum, we didn't need to write microservices to front the database, we didn't need to configure the database (not trivial if you want serializability https://blog.dbi-services.com/oracle-serializable-is-not-ser... ), we didn't need to write any cryptography code, we don't need to run any kind of infrastructure (let alone expensive, distributed infrastructure) to allow people to interact with and update the data. We get broadcasting of changes to clients so that the UIs can be kept up to date for free too.

We do have to carefully audit our smart contracts, but they are much smaller pieces of code than the microservices and triggers that we would otherwise have written.

Mainly, because our use case was similar to the crypto-asset tracking use case, there was a lot of code we could rely on already in ethereum that we would have had to write ourselves in the RDBMS world.

[icebraining]

Thanks. I have to admit I don't agree with most of that as stated, but I wasn't involved in the actual project, so I admit I may still be missing specifics.

By the way, did you use any historical data from the tracking? Does ethereum provide good tools to analyze that?