203
You probably don't need GraphQL
(mxstbr.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Apr 2024
203 points (97.7% liked)
Programming
17314 readers
97 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Love GraphQL, but oh man is it being over used at my company. Management sees success with one of our large apis, now all the little niche ones have to be migrated and everyone consuming them must migrate as well.
I like it, but the small 2 endpoint APIs that haven't changed in years, have small 5 field models and no related entities, has like 1 or 2 teams that consume them DO NOT need it.
LOL, "hey guys this thing hasn't changed in years, so we need you to convert your simple API request into a big ol' POST describing the entire model."
It's old, and therefore bad.
We really need a cultural change in this industry. Something that sits there doing its job for a decade+ with little to no change should be seen as a success.