SalarRahmanian  Nov 13, 2022
Is using #graphql a red flag 🚩 for #overengineering
Yes
22.2%
No
66.7%
It’s good for ones resume only 😂
11.1%
Poll ended at .
Show threadAdam
@softinio Always depends on the context of circumstances.
Nov 13, 2022 at 10:01pmWeb
Show threadJustin du CoeurNov 14, 2022

@adamsdesk @softinio Yeah, exactly. For *some problems* -- in particular, when your application is dealing with data structures that are being modified at runtime -- GQL is often the right tool for the job. (My own Querki is a fine example: GQL is the most sensible way to provide querying, given that the schemas are 100% runtime-defined.)

But if your API has static, consistent data types, then yeah -- probably over-engineering.

Show threadJay O’ConorNov 15, 2022
@jducoeur @adamsdesk @softinio Even if the schemas are pretty static, gql allows for evolving the schema over time in a manner far easier than versioning traditional REST or RPC APIs