Hey Paulie. Chris from GraphOps here. Thanks for your question!
At GraphOps we’re particularly excited about the protocol evolving to support a world of Data Services. This shift, from a single enshrined tech stack that can’t possibly meet every use case, to a diverse marketplace of data services, underscores the ecosystem’s commitment to make The Graph the foundational data layer of Web3.
There are so many exciting Data Services on the Horizon, but I have to make mention of GraphOps’ focus on File Data Service (FDS). FDS is a marketplace to share and monetise file data. Naturally, this has very broad applicability, but our initial focus is on supporting the real needs of Indexers within the Graph ecosystem today. Indexers are large-scale infrastructure operators, dealing with many terabytes of data. Much of this data is in the form of files: database backups, archive node snapshots and Firehose flatfiles. For Indexers that have already generated this data, FDS allows them to generate additional revenue by selling it to other Indexers. For Indexers that don’t yet have this data, it’s highly likely that someone will be willing to sell it to them at a cost that is lower than the cost of recreating it from scratch. This should increase the efficiency of The Graph, reducing time-to-data for Indexers and bolstering revenues.
In a year from now, we’d like to see FDS being actively used by Indexers to monetise and share their file data. Beyond the marketplace itself, we’d also like to see tooling developed that sits on top of FDS which automates adjacent actions like restoring a subgraph database backup from a file, and provides a seamless UX for Indexers to bootstrap a Subgraph or Firehose using data from FDS.
We’re also very excited about our ongoing work on Launchpad, our Kubernetes Toolkit for Indexers. We continue to believe that Kubernetes-centric infrastructure tooling is a critical piece of the puzzle to scale The Graph, and we’re actively working on adding Firehose and Substreams support to Launchpad. Next year, we’re excited to support both of these, alongside SQL, Files, and other emerging Data Services.
Outside of new Data Services, we’re excited to continue to see Graphcast impact the network positively in the areas of data determinism and network intelligence.
This barely scratches the surface of the developments that are being worked on across the Core Developer ecosystem, and we’re thrilled to be working alongside so many other smart and determined teams. Watch this space!
Hey Paulie. Chris from GraphOps here. Thanks for your question!
At GraphOps we’re particularly excited about the protocol evolving to support a world of Data Services. This shift, from a single enshrined tech stack that can’t possibly meet every use case, to a diverse marketplace of data services, underscores the ecosystem’s commitment to make The Graph the foundational data layer of Web3.
There are so many exciting Data Services on the Horizon, but I have to make mention of GraphOps’ focus on File Data Service (FDS). FDS is a marketplace to share and monetise file data. Naturally, this has very broad applicability, but our initial focus is on supporting the real needs of Indexers within the Graph ecosystem today. Indexers are large-scale infrastructure operators, dealing with many terabytes of data. Much of this data is in the form of files: database backups, archive node snapshots and Firehose flatfiles. For Indexers that have already generated this data, FDS allows them to generate additional revenue by selling it to other Indexers. For Indexers that don’t yet have this data, it’s highly likely that someone will be willing to sell it to them at a cost that is lower than the cost of recreating it from scratch. This should increase the efficiency of The Graph, reducing time-to-data for Indexers and bolstering revenues.
In a year from now, we’d like to see FDS being actively used by Indexers to monetise and share their file data. Beyond the marketplace itself, we’d also like to see tooling developed that sits on top of FDS which automates adjacent actions like restoring a subgraph database backup from a file, and provides a seamless UX for Indexers to bootstrap a Subgraph or Firehose using data from FDS.
We’re also very excited about our ongoing work on Launchpad, our Kubernetes Toolkit for Indexers. We continue to believe that Kubernetes-centric infrastructure tooling is a critical piece of the puzzle to scale The Graph, and we’re actively working on adding Firehose and Substreams support to Launchpad. Next year, we’re excited to support both of these, alongside SQL, Files, and other emerging Data Services.
Outside of new Data Services, we’re excited to continue to see Graphcast impact the network positively in the areas of data determinism and network intelligence.
This barely scratches the surface of the developments that are being worked on across the Core Developer ecosystem, and we’re thrilled to be working alongside so many other smart and determined teams. Watch this space!