Migrating Netflix to GraphQL Safely

Re:Migrating Netflix to GraphQL Safely by x86x87 on Sunday June 18, 2023 @09:54PM (#36386456)

In the beforefore time, you would need to establish a connection for every request you did if you wanted to make multiple requests in parallel and you were limited by how many request yoi could have in flight in parallel. With http2 you can mux the requests together through the same pipe. Yes, if you need to retrieve A to figure out you need B, it's not going to be "faster" but you would do the same thing on the server side.

Also, for a well architected backend you can spread load better on the backend and shockingly you can also leverage caching if you are doing a "dumb" rest api.

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by zeroonetwothree on Monday June 19, 2023 @10:04AM (#36391220)

GraphQL makes it straightforward to do conditional queries like:

  … on Book {
    title
    author
    if_viewer_can_purchase {
      price
      shipping
    }
  }

This is quite annoying to do with traditional REST without overfetching data you don’t need.

[ Parent | on HN ]