Content
@
0 reply
0 recast
2 reactions
Alex Loukissas π
@futureartist
I'm reaching a wider audience, so here's my question to all devs here who use graphql (with subscriptions): what are some good (and bad) patterns you've seen in action?
5 replies
1 recast
61 reactions
Mo
@meb
My main use for graphql is querying an external data source with lots of relations Otherwise for mutations, Iβm an RPC maxi
0 reply
0 recast
0 reaction
Aaron Ho Ο
@aho
Won't say I'm well versed with it but I think it's great when coupled with basic needs, e.g. A CMS list of items with customizable columns, row count, and pagination. It tends to get sloppy (query is a mess, execution is slow) when it comes to object nesting or deep relationships, adding filters on inner models. Sometimes the culprit is missing indexes, but it's not something you would know as you consume the resource. Lots of fine tuning needed via a DBA. It gets worst when you want to do complex aggregation, which I would end up write custom REST endpoints for. So I think depends what you wanna do with graphql...
0 reply
0 recast
0 reaction
Kindnesss.eth π
@kindness
Which service are you using?
0 reply
0 recast
0 reaction
Mark Carey π©π«
@markcarey
This is a good question. I am a reluctant graphQL user. While I do understand the benefits, I find the query syntax cumbersome. But I do find subscriptions intriguing ... but I haven't used them yet. Eager to learn more from others...
0 reply
0 recast
0 reaction
Maxinne ππΏ
@zuuye.eth
Just here for the replies
0 reply
0 recast
0 reaction
