search

JohnCorrigan1 / aave_v3_sps

0 stars 0 forks source link

Feedback on Substreams-powered subgraph developer experience #1

Open alex-pakalniskis opened 7 months ago

alex-pakalniskis commented 7 months ago

Hey @JohnCorrigan1

I'm Alex, a product manager working on the subgraph developer and Indexer experience. I see you've been busy developing many Substreams-powered subgraphs so was curious if you had any feedback on the developer experience (good or bad). Likewise, curious if you've checked out the new Substreams triggers as subgraphs mappings feature released as of graph-node v0.34.0.

Thanks and hope you are well, Alex

JohnCorrigan1 commented 7 months ago

Hey @alex-pakalniskis

Sorry for the delayed response. I have not been able to checkout the new triggers feature I will take a look.

The dev experience for Substreams powered Subgraphs is pretty great. I really enjoy writing rust and this kickstarted my dive into the graph ecosystem. The performance is insane and has made particular subgraphs possible or at least more feasible than they were before. The documentation for Substreams powered Subgraphs could use some enhancements, but the community in the Pinax and Streamingfast discords are very active and helpful which has more than made up for it.

The only major drawback I have run into is the data limit on store modules of 1GB. For most use cases this is a non issue, but for some broader subgraphs it can be a limiting factor. An example of this is aggregating the balance or holder count of a large token or many tokens. For this you would need to store an address and a balance of each address that interacts with the token. This can quickly exceed the 1GB limit. I understand the reasoning behind this limit, but it would be nice to have a way to increase it or some method to manipulate entity values of a subgraph from the Substreams. Currently you can replace entity values but the Substreams are blind to the current state of the subgraph. If there was some method to add to a field on an entity similar to the way store modules work instead of just set, it would solve this issue.

Overall I am very happy with the experience and the performance of Substreams powered Subgraphs and I don't see myself building "non-substreams powered subgraphs" anytime soon.