Pedro Diogo, Senior Technical Program Manager at The Graph Foundation, will go over The Graph's role as the indexing protocol in the web3 ecosystem. Pedro will cover how developers and data consumers are leveraging GraphQL to access open and public blockchain data. Pedro works closely with core developers of the protocol and technical ecosystem grantees helping build The Graph protocol.
Modeling, storing, and querying application data as a graph can help developers quickly get projects up and running by working with data the same way that we think about our domain: as a graph. In this talk we will explore how to apply this graph thinking technique to building GraphQL APIs using the Neo4j GraphQL Library and how we can leverage developer tools to go from idea to backend with nothing but graphs and GraphQL.
GraphQL has helped the industry realize the benefit of having typed APIs. But does that mean that if we switch over to a typed API like gRPC or OpenAPI then GraphQL is overkill? In this session, I want to discuss how GraphQL with Relay is critical to UI development and GraphQL without Relay leads us to reinventing the wheel on state management and API libraries again and again. And also as a corollary, how using GraphQL without Relay might not really be worth it!
Pedro Diogo, Senior Technical Program Manager at The Graph Foundation, will go over The Graph's role as the indexing protocol in the web3 ecosystem. Pedro will cover how developers and data consumers are leveraging GraphQL to access open and public blockchain data. Pedro works closely with core developers of the protocol and technical ecosystem grantees helping build The Graph protocol.
Modeling, storing, and querying application data as a graph can help developers quickly get projects up and running by working with data the same way that we think about our domain: as a graph. In this talk we will explore how to apply this graph thinking technique to building GraphQL APIs using the Neo4j GraphQL Library and how we can leverage developer tools to go from idea to backend with nothing but graphs and GraphQL.
GraphQL has helped the industry realize the benefit of having typed APIs. But does that mean that if we switch over to a typed API like gRPC or OpenAPI then GraphQL is overkill? In this session, I want to discuss how GraphQL with Relay is critical to UI development and GraphQL without Relay leads us to reinventing the wheel on state management and API libraries again and again. And also as a corollary, how using GraphQL without Relay might not really be worth it!
Get in touch!
hi@guild.host