EOS.IO Stack Exchange is a question and answer site for users and developers of distributed applications built on top of the blockchain operating system, EOS.IO. It only takes a minute to sign up.
Sign up to join this community
I have watched several tutorials for building DApps with EOS.
But, All they did in tutorials was deploying smart contract and storing data in the tables.
What is the point of doing that?(storing data can be done with normal database.)
Each action returns transaction id and what do we do with it?
What is overall workflow of DApp?
Can someone please give me explanation?
Its not about the storing of data, but about the authentification and authorization of that data. A blockchain allows you to know that a specific person performed a specific transaction.
Transaction IDs are useful for looking back into the history to understand what happened in the past. You can copy and paste a transaction ID into a block explorer such as bloks.io in order to see what happened in a particular transaction at some point in the past.
As for the overwall workflow of a dApp, that question is very broad, can you ask a new question and try to be more specific?
