Rest 2.0 graph ql
1 like124 views
This document introduces GraphQL as an alternative to REST APIs that allows clients to specify the exact data they need in a single request. It discusses some common problems with REST APIs, including making multiple roundtrips to fetch related data, over-fetching of unnecessary data fields, and difficulty for users to learn the API. GraphQL provides a solution by allowing clients to specify the fields and nested relationships they need in a single query, making it easier to fetch exactly the required data and reducing the need for documentation. Code examples are provided to demonstrate basic GraphQL queries for fetching and mutating nested data.
![GET /posts
、
{
posts: [
{
id: 1,
author_id: 101,
title: 'GraphQL in an Age of REST',
body: 'lorem ipsum',
votes: 342,
published_at: '2016-10-11T16:53:28+00:00'
}
]
}](https://image.slidesharecdn.com/rest2-170821064454/85/Rest-2-0-graph-ql-6-320.jpg)
![Problem 1: Multiple
roundtrips
GET /posts
、
{
posts: [
{
id: 1,
author_id: 101,
title: 'GraphQL in an Age of REST',
body: 'lorem ipsum',
votes: 342,
published_at: '2016-10-11T16:53:28+00:00'
}
]
}
GET /users/101
{
user: {
id: 101,
name: 'yosriady',
joined_at: '2015-10-11T16:53:28+00:00'
}
}
GET /users/103
GET /users/104
GET /users/105
。。。
处理理资源之间的关联就变成⼀一个灰⾊色地带](https://image.slidesharecdn.com/rest2-170821064454/85/Rest-2-0-graph-ql-7-320.jpg)
Rest 2.0 graph ql
- 1. ‘RESTFUL 2.0’ Is Here and Its Name Is GraphQL
- 3. Introduction to RESTFUL • GET /posts - Retrieves a list of posts • GET /posts/12 - Retrieves a specific post • POST /posts - Creates a new post • PUT /posts/12 - Updates post #12 • PATCH /posts/12 - Partially updates post #12 • DELETE /posts/12 - Deletes post #12 • http response 会附带着合适的HTTP Status Code，可以清楚知道这次请求的结果 • 例例如： • 200 OK • 400 Bad Request • 403 Forbidden • 404 Not Found 3
- 5. Data Model
- 6. GET /posts 、 { posts: [ { id: 1, author_id: 101, title: 'GraphQL in an Age of REST', body: 'lorem ipsum', votes: 342, published_at: '2016-10-11T16:53:28+00:00' } ] }
- 7. Problem 1: Multiple roundtrips GET /posts 、 { posts: [ { id: 1, author_id: 101, title: 'GraphQL in an Age of REST', body: 'lorem ipsum', votes: 342, published_at: '2016-10-11T16:53:28+00:00' } ] } GET /users/101 { user: { id: 101, name: 'yosriady', joined_at: '2015-10-11T16:53:28+00:00' } } GET /users/103 GET /users/104 GET /users/105 。。。 处理理资源之间的关联就变成⼀一个灰⾊色地带
- 9. Solution: Autoload related resources • GET /posts/1?embed=author.name { post: { id: 1, author_id: 101, title: 'GraphQL in an Age of REST', body: 'lorem ipsum', votes: 342, published_at: '2016-10-11T16:53:28+00:00', author: { name: 'yosriady' } } }
- 10. Problem 2: Over-fetching of data • APIs often return a huge JSON object with many fields, even when we only use a handful. • Solution: Clients should be able to specify the fields they only need • GET /posts/1?fields=title,link,published_at
- 11. Problem 3: How will users learn our API? • 调试接⼝口—麻烦 • Documentation
- 12. Why GraphQL ? • 多次请求获得数据 Multiple roundtrips • Facebook内部，⼤大量量不不同的app和系统共同使⽤用着许许多多 的服务api，随着业务的变化和发展，不不同app对相同资源的 不不同使⽤用⽅方法最终导致需要维护的服务api数量量爆炸式的增 ⻓长。 • 创建⼀一个⼤大⽽而全的通⽤用性接⼝口⼜又⾮非常不不利利于移动端使⽤用（流 量量损耗），⽽而且后端数据的⽆无意义聚合也对整个系统带来了了 很⼤大的资源浪费。 • 接⼝口需要完整API • 在这样的背景下，fb⼯工程师坐不不住了了，于是乎GraphQL的概 念就诞⽣生了了～最了了解客户端需要什什么数据的只有客户端⾃自⼰己， 所以如果给客户端提供⼀一种机制，让其表述⾃自⼰己所需的数据 结构，这岂不不是最合理理的么 ● A
- 13. 什什么是 GraphQL • A GraphQL query is a string interpreted by a server that returns data in a specified format. • 什什么⻤鬼？？ • (1) Query language • (2) Type system • (3) Runtime for client applications to fetch and mutate data.
- 14. “Talk is cheap. Show me the code.”
- 15. Hello GraphQL
- 17. Nested Data
- 19. Mutation