203
top 25 comments
sorted by: hot top controversial new old
[-] TheHottub@lemmy.world 34 points 8 months ago

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.

[-] jkrtn@lemmy.ml 9 points 8 months ago

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

[-] frezik@midwest.social 8 points 8 months ago

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.

[-] fubarx@lemmy.ml 31 points 8 months ago

The argument in the blog post sounds like one of those technologies that says "it works great once you have a billion users! Just wait and see."

Tried it once. It was a testing nightmare, trying to catch all the varying edge cases. Gave up and never looked back.

[-] deadbeef79000@lemmy.nz 9 points 8 months ago* (last edited 8 months ago)

Bold of you assume that any workplace where technologies are dictated by management has any kind of testing that matters.

Why are you testing that again? You tested that yesterday!

Submits resignation

[-] jkrtn@lemmy.ml 21 points 8 months ago

GraphQL is so stupid about collections of objects. If you want uniform pagination for different types of objects you have to write separate types for each.

I don't like how it composes things together. Kindof awkward when the subportions of the query need variables. Nested objects are great to form the query to just what one needs but then extra steps to decompose into what you'll actually have client-side.

[-] Cyberflunk@lemmy.world 14 points 8 months ago

Sounds like a bunch of people here don't understand the graphql use case or implementation. I've used it projects and works no worse than other solutions, and met the requirement of not having to update tons of code when queries are refactored. It's not right for everything, but the same is true for anything.

[-] MajorHavoc@programming.dev 12 points 8 months ago

I mean... Sure. I don't understand it. As long as I don't have to use it, we can leave it at that.

[-] flakpanzer@lemmy.world 6 points 8 months ago* (last edited 8 months ago)

At my workplace, we use it for East-West traffic, especially the central Identity, Authentication and Authorization service which every other service needs to access, and it works great for that use case (Since it allows the downstream services to fetch information however they like). REST can do that too, but it will be cumbersome to say the least. Although GraphQL performance has come under scrutiny lately.

this post was submitted on 14 Apr 2024
203 points (97.7% liked)

Programming

17610 readers
191 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 2 years ago
MODERATORS