davidbgk
/
larlet-fr-david
Прати 1
Волим 0
Креирај огранак 0
Код Издања 0 Activity
Repository with sources and generator of https://larlet.fr/david/ https://larlet.fr/david/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
896 Комити
1 Грана
Дрво: ffaa972798
Гране Ознаке
${ item.name }
Create branch ${ searchTerm }
from 'ffaa972798'
${ noResults }
larlet-fr-david/david/stream/2015/07/16/index.md

index.md 1.1KB
Датотека Normal View Историја

Add initial content
пре 4 година
​
​
​
​
​
​
​
​
​
​
​
 123456789101112 
  1. title: GraphQL et REST

  2. 

  3. > Current REST APIs can be exposed to GraphQL clients by building a GraphQL server as a wrapper around the REST API. A client would talk to a GraphQL server which would translate the query to (multiple) REST APIs. Client only sends one request, and receives the smallest possible response it needs. The server has much better bandwidth so the extra queries are not so critical.

  4. > 

  5. > <cite>*[GraphQL in the age of REST APIs](https://medium.com/chute-engineering/graphql-in-the-age-of-rest-apis-b10f2bf09bba)* ([cache](/david/cache/09f03c20156f63a521120c9dddda68f9/))</cite>

  6. 

  7. C’est ma conclusion également, [GraphQL](http://facebook.github.io/graphql/) ([cache](/david/cache/acd301ad06de4bf928f0515efa510a91/)) est très pertinent pour tout ce qui est *mashups* là où les multiples requêtes HTTP (1.1) de REST sont beaucoup moins efficaces. On pourrait aussi envisager une API hybride qui combine le meilleur des deux mondes :

  8. 

  9. * des ressources exposées en REST pour de l’unitaire ;

  10. * des points d’accès exposés en GraphQL pour les requêtes populaires.

  11. 

  12. Au prix des complexités à la fois côtés clients et serveur.