Развитие GraphQL тулинга привносит новые возможности работы со стороними сервисами. Я расскажу про свой опыт интеграции GraphQL c API Facebook/AWS/DevTools.

2. i’m roman
github: rastopyr
twitter: rastopyr_ua
software engineer
indiehacker
father

3. based on true story…

4. story 1
about product

5. redash.co
tracking ad perfomance

6. Marketing API

7. redash v1

8. support rest endpoints is hard
problem №1

9. /api/fb/campaings
/api/fb/campaings/:id/adsets
/api/fb/adsets
…
…
/api/fb/campaings/:id
support rest endpoints is hard

10. no REST - no pain

11. problem №2
SDK way
SDK

12. graphql is solution

13. 🎉 redash v2 🎉
with graphql

14. 🎉 redash v2 🎉
SDK

15. SDK in one place

16. SDK in one place
• validation
• aggregate requests
• pagination
• watch on limits
• …

17. facebook API endpoint
=
graphql resolver
facebook data type
=
graphql data type
no rest

18. relationships
in schema

21. graphql + TypeScript

22. code first way
SDL first way
and

23. code first way
1. define ts

24. define TS

25. code first way
1. define ts
2. implement resolver

26. implement resolver

27. 3. define gql types
1. define ts
2. implement resolver
code first way

28. define gql type

29. naming convention

30. 4. make schema
1. define ts
2. implement endpoint
code first way
3. define gql types

31. make schema

32. support static type checking

33. TS Definitions
Schema
API
type safe vertical
dev flow
direction
based on third party API

34. enough?

35. operations for computations

36. ROAS
Engagment Rate
operations for computations

37. update scheme on the fly
operations for computations

38. update scheme on the fly

40. cons

41. eat quota
•n + 1 ( cost analysis )
•big query ( queue in server )
•when service in scaling ( queue in infra )

42. save traffic
batch requests

43. pros

44. same patterns

45. type-safe
• TS interfaces for developers
• GraphQL API for clients

46. playground ❤️

47. story 2
about cloud

50. AWS have
~4000 methods

51. sdk
generated from scheme

52. service scheme

53. graphql scheme
generated from scheme

54. 1. generated from scheme
graphql server for AWS
2. map resolvers to sdk

55. aws graphql demo

56. Rastopyr/zlit-graphql-demos

57. graphql-compose/graphql-
compose-aws
alternative implementation

58. pros
•auto-generated
•extended
•sync with schema
•versioning out of the box

59. cons
•no way to query custom fields from sdk

60. story 3
about hooks

61. webhooks

62. API’s want say
webhooks

63. Event
POST call
to your URL
handle
request
webhooks

64. webhook payload

65. github
dropbox
stripe
bitbucket
mailchimp
facebook
sendgrid
twitter
hubspot twillio
and more…

66. how to handle webhooks
1.convert to gql query
2. map to gql type

67. webhook types in schema

68. isolated webhook resolver

69. realtime with Subscriptions

70. webhook
graphql
server
clients
realtime with Subscriptions

71. webhook graphql demo

72. Rastopyr/zlit-graphql-demos

73. pros
•custom resolver for custom webhook
•no dependencies
•based on empty graphql server

74. cons
•stateful

75. thanks!
twitter: rastopyr_ua
Rastopyr/zlit-graphql-demos