The Graph Subgraph Development and Querying Guide | ETHGlobal Workshop

Added:

Decentralized Data Lakes and Alternative Indexing Architectures

While The Graph is a pioneer in decentralized blockchain indexing, critics and competing protocols highlight significant limitations in its subgraph architecture. Developing and syncing subgraphs can be slow, costly, and complex due to the tight coupling of data extraction and transformation. Alternative architectures, such as decentralized data lakes (e.g., Subsquid) and modular indexers (e.g., Envio), offer faster performance by separating data extraction from presentation, allowing developers to query raw data and handle transformations off-chain using standard languages like TypeScript or Rust. Additionally, many developers still prefer centralized indexing services (such as Goldsky or Alchemy) to bypass the latency, indexing delays, and complex curation economics associated with The Graph's decentralized network coordination.

Fundamental understanding of blockchain concepts, Ethereum, and how smart contracts emit events.
Basic familiarity with GraphQL, including how to write queries and understand schemas.
Proficiency in JavaScript or TypeScript, as subgraph mapping handlers are written in AssemblyScript (a TypeScript subset).
An understanding of decentralized application (dApp) architecture and why indexing blockchain data is necessary.
Advanced subgraph design patterns, such as using data source templates for dynamically created smart contracts.
Optimizing subgraph indexing performance and implementing schema design best practices to prevent slow query times.
Deploying subgraphs to The Graph's decentralized network, understanding curation, and managing query fees using GRT.
Integrating queried subgraph data into frontend Web3 applications using clients like Apollo Client or Urql.
8.1K views191likes28:24@ETHGlobalOriginal Release: 2023-07-10

Subgraphs are instructions that developers provide to decentralized indexers to organize and make blockchain data queryable through GraphQL, enabling efficient access to historical blockchain data that would otherwise be difficult to read due to the read-heavy nature of blockchain interactions.