Upgrade to Pro — share decks privately, control downloads, hide ads and more …
Sign up for free

GraphQL 101

Avatar for Paulo Pires Paulo Pires
November 30, 2017
Programming
130
0

GraphQL 101

Avatar for Paulo Pires

Paulo Pires

November 30, 2017

More Decks by Paulo Pires

See All by Paulo Pires
Introdução ao WebAssembly
Avatar for Paulo Pires paulohp
0
71
Introdução ao GraphQL
Avatar for Paulo Pires paulohp
0
67
Side Effects: Uma Saga até o React
Avatar for Paulo Pires paulohp
0
100
MobX: State Management made easy
Avatar for Paulo Pires paulohp
0
110
Docker: The Rise of Containers
Avatar for Paulo Pires paulohp
0
140
We Work Remotely
Avatar for Paulo Pires paulohp
2
120
Angular2
Avatar for Paulo Pires paulohp
0
250
Node.js Codelab
Avatar for Paulo Pires paulohp
1
200
NodeBR, um ano memoravel!
Avatar for Paulo Pires paulohp
0
120

Other Decks in Programming

See All in Programming
モジュールの視点からSwiftを読み解く #iosdc
Avatar for Shigure Shimotori s_shimotori
0
290
技術的負債の返済は、AI時代の複利で効く投資 — 経営としての意思決定とその遂行
Avatar for curekoshimizu curekoshimizu
1
2k
機械に任せるテスト、人が見るテスト ⽣成AIで引き直した、運⽤保守フェーズの線引き
Avatar for KUSATAKE Daisuke dske104
0
110
ソニーのクラウド共通基盤の変遷と AI時代の開発スタイルに合わせた進化 / The Journey of Sony’s Common Cloud Platform and Its Evolution for AI-Native Development
Avatar for KenjiYoneyama kenjiyoneyama
0
200
UnityでSystem.Net.WebSocketsなWebSocketサーバが動かないのでUnity Monoのコードを覗いてみた / about implementing websocket server with unity mono
Avatar for にー兄さん drumath2237
1
520
Vue Fes Japan 2026 タイムテーブル徹底解説
Avatar for 448jp | OKI Yoshiya 448jp
1
580
AWS CDKのカスタムリソースでContinuum（旧Security Agent）を実装した話 | Implementing Continuum (formerly Security Agent) via AWS CDK Custom Resource
Avatar for アキキー | Akihisa Ikeda akihisaikeda
2
110
SREの越境 / SRE Collaboration
Avatar for y-ohgi y0hgi
2
290
WebRTC映像をAirPlayに対応させる挑戦.pdf
Avatar for monolithic-adam monolithic_adam
0
330
JAWS-UG 東京支部が始める、JAWS-UG支部コラボ / JAWS-UG lunchtime LT Collaboration
Avatar for y-ohgi y0hgi
0
170
JPUG勉強会 OSSデータベースの内部構造を理解しよう(第２回)
Avatar for Atsushi Ogawa oga5
0
290
Are APIs Still Relevant in the AI Era?
Avatar for Antoine Bluchet soyuka
0
390

Featured

See All Featured
Self-Hosted WebAssembly Runtime for Runtime-Neutral Checkpoint/Restore in Edge–Cloud Continuum
Avatar for Yuki Nakata chikuwait chikuwait
0
850
It's Worth the Effort
Avatar for 3n 3n
188
29k
Heart Work Chapter 1 - Part 1
Avatar for Lake Fama lfama
PRO
10
36k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
Avatar for Addy Osmani addyosmani
10
1.4k
Building Applications with DynamoDB
Avatar for Matt Wood mza
96
7.2k
Bioeconomy Workshop: Dr. Julius Ecuru, Opportunities for a Bioeconomy in West Africa
Avatar for AKADEMIYA2063 akademiya2063
PRO
1
380
A designer walks into a library…
Avatar for Paul Jervis Heath pauljervisheath
211
25k
エンジニアに許された特別な時間の終わり
Avatar for watany watany
109
250k
The MySQL Ecosystem @ GitHub 2015
Avatar for Sam Lambert samlambert
251
13k
[Rails World 2026] Durable orchestration on Rails: from continuation to workflow
Avatar for Vladimir Dementyev palkan
1
410
The Mindset for Success: Future Career Progression
Avatar for Greg Gifford greggifford
PRO
0
520
How to Talk to Developers About Accessibility
Avatar for Jason CranfordTeague jct
2
560

Transcript

  1. GraphQL 101 @caofrade

  2. Objetivo

  3. GraphQL Novo padrão para APIs Linguagem de Query (consulta) Open-source

    mantido pela galera do Facebook

  4. Quem usa?

  5. MUITO, MAS MUITO CONTEUDO

  6. HYPE? Que problema o GraphQL resolve mesmo?

  7. REST

  8. REST •Representational State Transfer •Arquitetura baseada em recursos: - Entidades

    do sistema - Identificados por URIs - Manipulado por representações (JSON, XML, HTML)
  9. None
  10. None

  11. Problemas •Overfetching - Download de dados desnecessários. •Underfetching - Acessar

    mais de 1 endpoint para juntar os dados necessários.

  12. GraphQL

  13. Conceitos

  14. Schema •Recursos são definidos por um sistema de tipos •Contrato

    entre cliente e servidor sobre como a aplicação pode acessar os dados. •Schema Definition Language (SDL)
  15. None

  16. Query •No REST, múltiplos endpoints retornam estruturas de dados fixas.

    •Em GraphQL, existe um único endpoint, onde o cliente determina qual dado é necessário.
  17. None
  18. None
  19. None
  20. None

  21. Mutation •Responsável por criar e mudar dados armazenados no back-end.

  22. None
  23. None

  24. Schema •Query e Mutation também precisam ser definidos no Schema

    •São os pontos de entrada para as requisições enviadas pelo cliente.
  25. None

  26. Como Usar?

  27. facebook.github.io/relay

  28. apollographql.com/client

  29. GraphQL não é magica!

  30. E não vai matar o REST!

  31. Obrigado @caofrade