like

great piece

Hi great article, love the analogy.

I just have one question bare with me as I've overcomplicated it in my head but with web3.0 being decentralised with no one entity controlling it, how is the site paid for? I need help removing the massive web hosting companies from the picture.

Would it function similarly to PRESEARCH? you have a bunch of nodes all over the world accepting users requests and getting paid for being a node or would the user connect their metamask wallet etc.

If there is no centralised database with the data solely with the user client-side... idk my brain is a mess.

Also Web3.0 sites seem to all be ETH, what about the gas fees? they are silly high etc.

Would you be able to explain a simple web3.0 concept like a blog or something? A real-world simple concept. Thanks

Congratulations on your first craft 🎉🎉

Nice and simple explanation :Cheers:

I have to jump in here and be a voice of reason (call me a party pooper but I've been around long enough to feel a buzz coming from far away). "Trigger happy" is the cowboy term that comes to mind when people make brave clairvoyant predictions like this. You have to realize that some of these concepts you are talking about have existed in some form (first theoretical, then different practical approaches to implementation). Creating a buzz will get you a few blog posts and likes but it won't change the fact that you're trying to oversell something I'm suspecting you don't quite realize and understand completely.

Let me roughly try to guide you trough the stages of a system (web based since you're talking Web 3.0 here)

1. The request response way of communication is the first and most optimal for usage when your system is small and you don't have that many users.

2. When userbase increases you start optimizing by maybe CQRS pattern. Most likely when you need to redesign your system around when you reach ~100K - 1M users This is when you maybe introduce orchestration and similar approaches as you might need to dynamically scale.

3. 1M+ you start restructuring and redesigning to accommodate for the fact that you will need to split every step of the flow and decide based on operation how fast should you get it back. Most probably something event based, cached, scaled, using real-time signaling etc.

** 10M+ is around the beginning of a new stage of development of a system that is simply too big for one approach you have to further drill down each operation and the way it goes trough the system. But, the timespan you have is so short that you need to start making compromises. One of the approaches you could take here is go for a paradigm called "eventual consistency" and use event-store systems. THIS IS WHERE BLOCKCHAIN could come in as a concept. Eventual consistency is an approach where a lot of operations are event based and asynchronous. They are all over the place. Some mechanism has to make sure that they are all structured and that the order of operations is known. Again you could use blockchain but there are more efficient ways to achieve this.

I just simply cannot see why and how a consensus would be achieved in the web community and the governing bodies around www etc. would even suggest such a thing - forcing a very specialized concept on areas where we don't need them.

Hope this just encourages you to learn stuff more in-depth before you start making predictions and assumptions.

Good luck!

I love your article! It is something new for me)

But I was wondering, in how many years do you think we will be able to transit from Web 2.0 to Web 3.0? and do you think it is the right time to start learning blockchain programming, so when web 3.0 comes we will be ready to go right into the work?

Thanks in advance!

thanks

This is really nice 👌 thanks for sharing 💙