document authentication

[rafaelkrapf]

Let's say I would like to generate signed documents and allow someone to see if it is authentic.
Let's say I would like to use an ordinary database instead of the blockchain, storing a PDF version of the document in the database.
Let's say I would like to run the system in a service provider.

Where could I host this system?
What database can I use?

[arun664]

The signed documents details are pushed to Ethereum blockchain network using smart contract (more clear and concise this contract is. Better the gas fee). The transaction id can be used retrieve details and present it to the user, which can also be verified using just the identity details of that certificate id/user id which are stored in database of the ISSUER.

If you use ordinary database instead of blockchain to store pdf, think about data integrity as well. Since the main purpose here is to ensure data is secured and cannot be modified. You can use combination of file/data like storing the CHECKSUM/HASH value of the file onto blockchain.

You can use any service provider depending of cost and SLAs.

It can be hosted on public cloud or on prem, depending on security and accessibility for your users.
MongoDB Cloud (NoSQL) is used since dealing with docs and json data which was much easy. But any other database can be used as well depending on your need.

Hope this helps! @rafaelkrapf

[rafaelkrapf]

Thank you, helpful for sure, I'll do more research on the topic.
Thank you, @arun664