Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
dawufi pfp
dawufi
@dawufi
devs - pls halp https://www.weponder.io/surveys/1197
13 replies
4 recasts
24 reactions
Ben Adamsky 💭 pfp
Ben Adamsky 💭
@ba
Depends on the service, there's no right answer for how providers expose the data they're indexing We're currently using thirdweb which is composed of rest apis under the hood, but they could have easily used SQL (Dune) or GraphQL (Airstack) if they wanted to
2 replies
0 recast
2 reactions
King pfp
King
@king
Hmmm rest or graph and then cache to Postgres (redis vectorized better).
2 replies
0 recast
1 reaction
slingn.eth pfp
slingn.eth
@slingn
Depends on the use case imo - how do you plan on looking up data and what specifically are you looking to index vs pull on demand
1 reply
0 recast
0 reaction
matt 💭 pfp
matt 💭
@matthewmorek
like many others mentioned this is highly contextual, but you can apply some general heuristics if you’re after just ephemeral read on-the-fly, then probably REST/GraphQL with some light caching if you’re building sth where you’re using onchain data to connect to your own data, caching in SQL+Redis works
1 reply
0 recast
0 reaction
Joe Petrich 🟪 pfp
Joe Petrich 🟪
@jpetrich
Depends what you're querying, how often, how up to date you need it, and then what you're going to do with it. If you're building an indexer, you want to be hitting a node directly or running your own. If you're building a dashboard, probably just use Dune. For almost nothing use BigQuery; their public dataset sucks.
1 reply
0 recast
0 reaction
Colin Johnson 💭 pfp
Colin Johnson 💭
@cojo.eth
Cc @ba @matthewmorek
1 reply
0 recast
0 reaction
lucky pfp
lucky
@lsankar.eth
don’t understand the question do you mean how to serve?
1 reply
0 recast
0 reaction
ivyroot pfp
ivyroot
@ivyroot
some questions that help decide between those options are: How connected are the server-side and frontend dev teams? If low connection prefer GraphQL. How many different resources are there onchain? If low number prefer REST or Postgres. BigQuery seems like a reporting/stats option, not for interactive DAPPs.
1 reply
0 recast
0 reaction
chinmay.eth pfp
chinmay.eth
@chinmay.eth
It depends. @betashop.eth 's Airstack might be perfect, if you want to avoid coding.
1 reply
0 recast
0 reaction
iSpeakNerd 🧙‍♂️ pfp
iSpeakNerd 🧙‍♂️
@ispeaknerd.eth
no idea but interested in results 👀
1 reply
0 recast
0 reaction
Leeward Bound pfp
Leeward Bound
@leewardbound
impossible to answer without context about queried data, access frequency, intended clients, engineering resources available, project scope and timeline, all 4 are very appropriate in different situations
1 reply
0 recast
0 reaction
limone.eth 🍋 pfp
limone.eth 🍋
@limone.eth
GraphQL cause there’s a lot of data and it’s easier to manipulate/customize
2 replies
0 recast
0 reaction
Ponder Surveys pfp
Ponder Surveys
@survey
Survey has ended after 48 hours and received 65 votes.
0 reply
0 recast
0 reaction