graphql
- Engineering
- Last Updated: June 24, 2020
- Owen Ou, Chris Castle
Over the last few years, GraphQL has emerged as a very popular API specification that focuses on making data fetching easier for clients, whether the clients are a front-end or a third-party. In a traditional REST-based API approach, the client makes a request, and the server dictates the response: $ curl https://api.heroku.space/users/1 { “id”: 1, “name”: “Luke”, “email”: “luke@heroku.space”, “addresses”: [ { “street”: “1234 Rodeo Drive”, “city”: “Los Angeles”, “country”: “USA” } ] } But, in GraphQL, the client determines precisely the data it wants from the server. For example, the client may want only the user’s name and email,…
Subscribe to the full-text RSS feed for Owen Ou.