Jul 25, 2017 · 1 min read
- The need to do multiple round trips to fetch data required by a view: Does this also means you don’t get any data until the slowest piece of data is retrieved?
- Clients dependency on servers: Don’t get your argument. Both REST and GraphQL have an API/Schema, you are coupled to that.
- The bad front-end developer experience: Limiting the data returned. Jenkins REST API has been doing this with a query parameter for an extremely long time.