Graphql a goodbye to massive datas, the basic what you need to know

Transcript

1. A goodbye to massive datas, the basic what you need to know Tauan Tathiell de Aleluia Camargo Helio Vitorino Soares Junior
2. About us Tauan Tathiell / @lukyhenson ➢ Developer at Codeminer42 Helio S. Junior / @hjJunior ➢ Developer at Codeminer42
3. Created by
4. That is a new way to Build sql?
5. DEfinitely no!
6. So, what is graphql?
7. VS
8. What is rest?
9. REST: Representational State Transfer • History • Architecture Model • Resources based in endpoints(URL’s) • Works with the HTTP verbs [GET, POST, PUT, PATCH, DELETE]
10. Was created by Roy Fielding and he defended the REST pattern on his doctorate degree in 2000, but REST has been developed in between 1996 - 1999. HIstory
11. 2000’s
13. THE REST ARCHITECTURE WAS NOT DEVELOPED FOR THE APPLICATIONS, DEVICES AND USERS OF TODAY.
14. Rest lifecycle API AS PRODUCT Design Develop Measure api/v1 api/v[infinity]
15. Architecture Model
16. HTTP VERBS AND ENDPOINTS
17. Which kind of problems we have in rest api’s?
18. 1° Versioning
19. 1° versioning
21. 2° multiples endpoints
22. Example
23. 3° the endpoints show more than necessary data
24. 4° rest is schemaless
26. Is Graphql The savior of the motherland?
27. no, But it can help you improve your api!
28. Why Graphql?
29. GRAPHQL concepts
30. 1° SINGLE ENDPOINT
31. 2° It works with schemas :D
32. 3° no more OVERFETCHING
33. 4° no more UNDERFETCHING
35. The architecture
36. query It expect to get information Mutation It expect to make changes Subscription Websocket to real time changes
37. Getting started A simple example of fetch { myShop { name location { city address } products(orderby: POPULARITY) { name price } }
38. The result One endpoint | One fetch { "myShop": { "name": "Full Stack Fest Shop", "location": { "city": "Barcelona", "address": "Av. Diagonal 547" }, "products": [ { "name": "Conferece Ticket", "price": 5000.99 }, { "name": "Cool T-Shirt", "price": 2000.10 } ] }
39. And about the documentation?
40. Did you remember about the stronger typed?
41. Live code...
42. So….
43. Which one do you prefer?