![\"Traditional](\"/static/a6cd14146c32fa8ba147ea689c92acf7/5d442/api.png\" "\\"Traditional")
\n \n The Web3 revolution is just getting started, eliminating the irregularities of the centralized Web 2.0.
\nThe main difference between Web2 and Web3 is decentralization. Web3 builders re-design the internet itself from the ground level, giving back the ownership to its participants. So that, one corporation cannot have control and make important decisions for us. The Graph has become an essential part of developing Decentralized apps by making life easier for Web3 developers.
\nOne of the main hurdles of developing a decentralized application (dApp) is the complexity of querying and using data from a blockchain.
\nLet us imagine, a developer is building a betting game based on Web3. He wants to display the total games lost/won and update it whenever someone plays again. It is not so difficult to do in the traditional way. Let us say, he wants to display the amounts of bets lost/won only for a specific player. Well, we are out of luck. In this case, he needs to deploy a new contract that stores those values and fetches them . One project aiming to change this situation is The Graph. It makes dApps development easier for the developer, by indexing and making subgraphs.
\n\n \n The Graph is an indexing protocol with decentralized abilities. It is an integral part of Web3, considering that it is a vital addition needed to provide seamless data for decentralized applications (DApps).
\nTo understand Graph protocol, we have to understand indexing, the main idea behind The Graph. Indexing reduces the time required to find a particular piece of information.
\nIt is like an index in a book. To find a concept, instead of going through the whole book page by page, we can find it much quicker in the index. Which is sorted alphabetically and contains a referral to the actual page.
\nDatabase indexes do the same thing in computer science, cutting the search time by indexing the whole database.
\n![\"The](\"/static/05387069e3ee9ed959c265ef6a6a1a29/29018/graph.png\" "\\"The")
\n \n As Web3 use cases grow, it’s important to remember what separates Web3 from the centralized web, so that we don’t repeat the mistakes of the past. Dapps must run on a fully decentralized protocol. Any points of centralization can and will be abused to lock people in and gain market advantage.
\nThe Graph comes into play as an enabler of decentralized internet applications that will be completely facilitated by public infrastructure.
\nTo build a decentralized application the indexing layer must be also decentralized. You can have a decentralized blockchain, but if a user is interacting with it through a centralized service, you’ve now reintroduced centralization. You now have other companies making decisions around the state of the information and what information is true.
\nAccording to Yaniv Tal, cofounder of The Graph, “the nodes running The Graph are all decentralized, the smart contracts they run are also decentralized, and the indexers are decentralized”. Yet, its technology has underpinned a wide swath of crypto applications, from the most popular to up-and-comers.
\nImagine you’re building Google today — the Graph is doing a similar thing. It’s gathering all this public information on all these blockchains. The difference between Google and the Graph is The Graph is doing it all open source and decentralized.
\nThe Graph protocol’s ability to create a global grid of public information, helps eliminate the need for projects to develop and operate proprietary indexing servers. Using The Graph saves time and money, typically spent on engineering and hardware resources. So developers can provide next level decentralized applications with amazing abilities that will surpass the usual expectations that users have.
\n![\"The](\"/static/dc4eaafcc45ab67adf6cd9a4a00da560/5d442/end.png\" "\\"The")
\n \n