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
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
73
Introdução ao GraphQL
paulohp
0
68
Side Effects: Uma Saga até o React
paulohp
0
110
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
AIが生成したコードは読むべきか?抽象化設計とコードの品質保証 / abstraction-design-and-quality
minodriven
12
7.7k
AI時代のFlutter品質設計 — アプリ品質を守るQuality Layers
omatty198
0
320
Herb in Rails 8.2: Your ERB views, now HTML-aware @ Kaigi on Rails 2026, Tokyo, Japan
marcoroth
2
370
最近”作らせてる” ローカルAIアプリの話
akit37
0
520
現場と育てるRailsモデリング 〜Spreadsheetから始めたモデル設計〜
siroemk
2
1.1k
PumaからFalconに移行したRailsアプリケーションでの実践
falcon8823
0
300
AI時代のIaC入門 〜なぜインフラをコードで管理したいのか?〜 / Introduction to IaC in the AI Era
akihisaikeda
5
1.3k
ActionController meets Protocol Buffers
sorah
1
750
React Native에 현대적인 빌드 도구 더하기: Rollipop 구현기
leegeunhyeok
0
170
LLM 101
dalinaum
0
370
作って学ぶSpring BootのAuto Configuration / JJUG Night Seminar 2026-10-19
rshindo
0
210
Spec-Driven Development - Why Vaadin Is the Perfect Fit
simas
PRO
0
190
Featured
See All Featured
How to Build an AI Search Optimization Roadmap - Criteria and Steps to Take #SEOIRL
aleyda
1
2.2k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
287
14k
Navigating Algorithm Shifts & AI Overviews - #SMXNext
aleyda
1
1.7k
More Than Pixels: Becoming A User Experience Designer
marktimemedia
3
600
Context Engineering - Making Every Token Count
addyosmani
9
1.3k
brightonSEO & MeasureFest 2025 - Winning Strategies for Black Friday CRO & PPC - Christian Goodrich
cargoodrich
3
880
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
Building a A Zero-Code AI SEO Workflow
portentint
PRO
0
800
GraphQLの誤解/rethinking-graphql
sonatard
75
12k
Gemini Prompt Engineering: Practical Techniques for Tangible AI Outcomes
mfonobong
2
610
Ruling the World: When Life Gets Gamed
codingconduct
0
430
世界の人気アプリ100個を分析して見えたペイウォール設計の心得
akihiro_kokubo
PRO
74
43k
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