Architecture of a DApp
Figure 4.1 represents an Ethereum DApp at a high level. If you notice, every client browser communicates with its own instance of the application. There is no central server to which all clients connect. This means, every person who wants to interact with a decentralized application will need a full copy of the blockchain running on their computer/phone, and so on. That means, before we can use an application, we have to download the entire blockchain and then start using the application. This might sound ridiculous at first but it has the advantage of not relying on a single central server that might disappear tomorrow, or start charging us third-party commissions.
To build web-based DApps, Ethereum comes with a handy ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access