What’s the distinction between web2 & web3, actually? Sure, there are tokens and preliminary coin choices and drops and discords. However, at present, they resemble one another fairly a bit.
Right here’s my psychological mannequin:
Think about a startup that sells sports activities playing cards. A web2 structure for this app would have 5 components
- A transaction database: consumer 1 bought card ABC to consumer 3.
- A metadata database: consumer 1’s first identify is Samuel and his profile image is discovered at this URL.
- File storage: the profile image file is saved right here.
- App server: the code that runs the appliance.
- IaaS/CDN (Infrastructure as a Service / Content material Supply Community): the servers that run code.
Examine this picture to a web3 structure with the web3 components in purple.
Solely the transaction database & the file storage modified shade.
We swapped the transaction database from PostGres to a blockchain like Ethereum or Sui, and the file storage from AWS S3 to a decentralized storage supplier, maybe Filecoin or ArWeave.
Makes me surprise: If the database APIs have been the identical throughout web2 & web3, would builders or customers discover?
The remainder of the appliance stays Web2, operating on Amazon, Google or Microsoft servers. Many builders construct web3 purposes this manner: video games, exchanges, cross-chain bridges.
The remaining components of the stack haven’t been recast as decentralized providers, but. Maybe they are going to be.
For now, the transaction database stays probably the most crucial decentralized part. That’s sufficient to confer the advantages of decentralization to customers, whereas giving engineers the instruments to construct a practical app.