A place for developers to talk about building on Farcaster.

/dev

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?

enzo's dad 🇬🇷 in LA 🌴 eng @ fanatics.live ⚾️ alexloukissas.com

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...