Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
GraphQL 101
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Paulo Pires
November 30, 2017
Programming
130
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
GraphQL 101
Paulo Pires
November 30, 2017
More Decks by Paulo Pires
See All by Paulo Pires
Introdução ao WebAssembly
paulohp
0
71
Introdução ao GraphQL
paulohp
0
67
Side Effects: Uma Saga até o React
paulohp
0
100
MobX: State Management made easy
paulohp
0
110
Docker: The Rise of Containers
paulohp
0
140
We Work Remotely
paulohp
2
120
Angular2
paulohp
0
250
Node.js Codelab
paulohp
1
200
NodeBR, um ano memoravel!
paulohp
0
120
Other Decks in Programming
See All in Programming
SREの越境 / SRE Collaboration
y0hgi
2
300
JRuby: Past, Present, and Future
headius
0
230
Everything will be SERVERLESS — 信じて運用した10年の経験値 / Everything Will be Serverless — Lessons Learned from 10 Years of Operational Experience
seike460
PRO
1
900
プロダクトコードからライブラリの境界を見つける
elmetal
PRO
0
110
Vue Fes Japan の “作る側”に関わってみて
naokihaba
0
140
Simple Storage Service(S3) is not simple
iwatsukayura
0
230
Apple Intelligence を用いた個人情報誤送信防止、及びユーザーリクエスト体験の改善について
yukiny
0
320
技術的負債を組織課題として解く-増えすぎたマイクロサービスとの戦い-
reimaru
1
2.9k
[ハンズオン]AIへの指示だけで「五目並べ」を作ってみよう
satoshi256kbyte
1
360
ソニーのクラウド共通基盤の変遷とAI時代の開発スタイルに合わせた進化 / The Journey of Sony’s Common Cloud Platform and Its Evolution for AI-Native Development
kenjiyoneyama
0
240
半永久的に提供し続けられるプライベートクラウドを目指して ― 利用者の認知負荷を抑えるAPI抽象化とハードウェア世代交代の基盤設計
tomokon
0
470
Starting & Sustaining Code-Based E2E Testing for Non-Coding QA Teams( #jasstniigata )
teyamagu
PRO
1
950
Featured
See All Featured
Bash Introduction
62gerente
615
220k
Un-Boring Meetings
codingconduct
0
450
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
287
14k
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
minecr
1
420
VelocityConf: Rendering Performance Case Studies
addyosmani
331
25k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
31
3.4k
Rebuilding a faster, lazier Slack
samanthasiow
85
9.7k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
46
3k
From Legacy to Launchpad: Building Startup-Ready Communities
dugsong
0
350
HU Berlin: Industrial-Strength Natural Language Processing with spaCy and Prodigy
inesmontani
PRO
0
740
Heart Work Chapter 1 - Part 1
lfama
PRO
10
37k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
130k
Transcript
GraphQL 101 @caofrade
Objetivo
GraphQL Novo padrão para APIs Linguagem de Query (consulta) Open-source
mantido pela galera do Facebook
Quem usa?
MUITO, MAS MUITO CONTEUDO
HYPE? Que problema o GraphQL resolve mesmo?
REST
REST •Representational State Transfer •Arquitetura baseada em recursos: - Entidades
do sistema - Identificados por URIs - Manipulado por representações (JSON, XML, HTML)
None
None
Problemas •Overfetching - Download de dados desnecessários. •Underfetching - Acessar
mais de 1 endpoint para juntar os dados necessários.
GraphQL
Conceitos
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)
None
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.
None
None
None
None
Mutation •Responsável por criar e mudar dados armazenados no back-end.
None
None
Schema •Query e Mutation também precisam ser definidos no Schema
•São os pontos de entrada para as requisições enviadas pelo cliente.
None
Como Usar?
facebook.github.io/relay
apollographql.com/client
GraphQL não é magica!
E não vai matar o REST!
Obrigado @caofrade