from Hacker News

GraphQL at PayPal: An Adoption Story

by arberavdullahu on 9/1/21, 12:47 PM with 5 comments

• by mbStavola on 9/1/21, 4:21 PM

  As someone who is exploring a GraphQL "migration" for a rather large project, I'm interested to hear more about the issues in practice from people who've had to work in GraphQL environments on long timescales. I see a lot of the pro-GraphQL people talking up the advantages but never really the drawbacks.

  I've had some concerns about GraphQL in the past when it was first coming up, but they look to be mostly addressed in some way shape or form. For example, using a CDN is now viable without hacks if you utilize something like Apollo Persisted Queries. Most of the research I've done on the topic recently has come up with a lot of outdated criticisms.

  On that note, it almost feels as if people wrote off GraphQL in the beginning and have largely ignored the developments since. The people already on board the train seem to write more to an existing audience of users rather than people looking to get in.

• by switch007 on 9/1/21, 2:21 PM

  > Avoid multiple round trips: Often, in order to call one endpoint that required a certain parameter, such as /getProfileById/{id}, we would have to call additional endpoints as a pre-req, such as getUser{username} to returnparameters such as id. This was a problem because we were making multiple round trips to fetch one piece of information. GraphQL helped solve this problem because it allowed us to fetch everything we need in one round trip.

  Why not add another URL? /getProfileByUsername?

  Nothing stops you building another layer of endpoints to service your frontend.