The power of Serverless GraphQL with AppSync - AWS Community Day Bosnia 2020

Transcript

1. he!o! AWS Community Day Bosnia
2. every story n"ds a hero
5. Our hero
6. Works in a sma! team on a mid-sized application
7. Most of the time enjoys the job
8. Just sent a test push notification to thousands of customers
9. We need to build this new complex app.
10. Ok, no problem
11. But we have a short deadline.
12. Ok, how short?
13. It needs to be ready for yesterday. And it needs to be scalable and real-time!
14. …
15. How should I build this?
16. Don't worry, we have a famous consultant that will help you architecture the app.
17. Great!
18. multi-cloud guru
19. Just use Kubernetes! multi-cloud guru
20. But I don't know Kubernetes.
21. I don't have time to learn Kubernetes now.
22. What should I do?
23. Am I the only one who don't know Kubernetes?
24. Maybe I am not good enough for this!
26. Serverless GraphQL You should try
27. Serverless GraphQL?
28. Serverless GraphQL with AppSync The Power of
29. @slobodan_ Before we continue…
30. Slobodan Stojanović CTO @ Cloud Horizon & CTO @ Vacation Tracker co-author of Serverless Applications with Node.js book AWS Serverless Hero @slobodan_
31. Serverless GraphQL with AppSync The Power of
32. Serverless GraphQL
33. Serverless GraphQL ?
34. What's GraphQL?
35. @slobodan_ "Our biggest mistake was betting too much on HTML5" Mark Zuckerberg, 2012
36. @slobodan_
37. @slobodan_ HTML HTML
38. @slobodan_ "Our biggest mistake was betting too much on HTML5" Mark Zuckerberg, 2012
39. @slobodan_ REST? FQL? REST? FQL?
40. @slobodan_ "We were frustrated with the differences between the data we wanted to use in our apps and the server queries they required." L" Byron, 2015 GraphQL: A data query language article
41. @slobodan_ Data app needs Data app needs
42. @slobodan_
43. Nice. But, why should I care about GraphQL?
44. I don't have the same problems as Facebook.
45. Ok, but let's s" if you have one of the fo!owing problems
46. Distinct frontend clients for multiple platforms (i.e., web and mobile) has different data requirements.
47. A backend serves data to clients from different sources.
48. A complex state and caching managements for both frontend and backend.
49. Slow pages especia!y on mobile, caused by multiple dependant HTTP requests.
50. These are just some "symptoms" that GraphQL can cure.
51. • Defines a data shape • Hierarchical • Strongly typed • Protocol, not storage • Introspective • Version fr"
54. Types type Author { id: Int name: String posts: [Post] } type Post { id: Int title: String text: String author: Author }
55. Schema type Query { getAuthor(id: Int): Author getPostsByTitle(titleContains: String): [Post] } schema { query: Query }
56. Resolvers getAuthor(_, args){ return sql.raw('SELECT * FROM authors WHERE id = %s', args.id); } posts(author){ return request(`https://api.blog.io/by_author/${author.id}`); }
57. Queries { getAuthor(id: 5){ name posts { title author { # this will be the same as the name above name } } } }
58. 1. Parse 2. Validate 3. Execute
59. Result { "name": "Slobodan", "posts": [{ "title": "Hello World", "author": { "name": "Slobodan" } }, { "title": "GraphQL", "author": { "name": "Slobodan" } }] }
60. GraphQL supports: • Queries • Mutations • Subscriptions
61. Interesting!
62. Serverless GraphQL
63. Serverless GraphQL Why?
64. GraphQL using Kubernetes We!, you can deploy
65. BUT there's an easier way
66. You sti! n"d to scale these
67. Unless you make it serverless
68. How can I make my GraphQL app serverless?
69. You can make it manua!y
70. Or you can use AWS AppSync!
71. What's AWS AppSync?
72. AppSync is a managed service that uses GraphQL to make it easy for applications to get exactly the data they n"d.
73. AppSync to develop your app faster You can use
74. I can? How?
75. • Define GraphQL schema • Automatically provision a DynamoDB data source and connect resolvers • Write GraphQL queries and mutations • Use the API in the frontend app
76. It's easy to start with Let's give it a try
77. You can start with the guided schema wizard on AWS Web Console
78. But you should use AWS Amplify, CloudFormation or CDK for more serious apps
80. > amplify init > amplify add api > amplify push
81. Wow, that was fast!
82. I should show it to the consultant.
83. That will never work! Amplify is not good enough. multi-cloud guru
84. You can always start with Amplify and then move to CloudFormation or CDK
85. AppSync with CDK import * as cdk from '@aws-cdk/core'; import * as appsync from '@aws-cdk/aws-appsync'; export class AppsyncCdkAppStack extends cdk.Stack { constructor(scope: cdk.Construct, id: string, props?: cdk.StackProps) { super(scope, id, props); // Creates the AppSync API const api = new appsync.GraphqlApi(this, 'Api', { name: 'my-awesome-app', schema: appsync.Schema.fromAsset('graphql/schema.graphql'), }); // Prints out the AppSync GraphQL endpoint to the terminal new cdk.CfnOutput(this, "GraphQLAPIURL", { value: api.graphqlUrl }); } }
86. Ok, but the app needs to be real-time multi-cloud guru
87. AWS AppSync lets you specify which part of your data should be available in a real-time manner using GraphQL Subscriptions.
88. Real-time subscriptions type Subscription { addedPost: Post @aws_subscribe(mutations: ["addPost"]) updatedPost: Post @aws_subscribe(mutations: ["updatePost"]) deletedPost: Post @aws_subscribe(mutations: ["deletePost"]) }
89. And it needs to be scalable! multi-cloud guru
91. But what if you need a search functionality? multi-cloud guru
92. AWS AppSync supports Amazon Elasticsearch! the GraphQL operations can be simple lookups, complex queries & mappings, fu! text searches, fuzzy/keyword searches or geo lookups.
93. But what if you need to connect to an existing app? multi-cloud guru
94. You can connect AWS AppSync to AWS Lambda!
95. What about roles and permissions? multi-cloud guru
96. • API_KEY Authorization • AWS_IAM Authorization • OPENID_CONNECT Authorization • AMAZON_COGNITO_USER_POOLS Authorization
97. Multi-tenant? multi-cloud guru
98. You can use Cognito Groups.
99. use Resolver Mapping Template For fine-grained permissions
100. ? multi-cloud guru
101. ?
102. You can use Apache Velocity Template Language (VTL)
103. What's VTL?
104. I would say it’s an alien language (we!, its Java-based) hard to test in isolation in a serverless application, especia!y in AWS CloudForamation.
105. Alien language a.k.a. VTL #if($context.result["Owner"] == $context.identity.username) $utils.toJson($context.result) #else $utils.unauthorized() #end
106. Ha! I don't like that! multi-cloud guru
107. Me neither!
108. AppSync supports Direct Lambda Resolvers, which skips VTL completely
109. But what if you want to reuse some logic? multi-cloud guru
110. You can do that in AWS Lambda or use Pipeline Resolvers
111. Ok, ok, but this is still complex for the frontend multi-cloud guru
112. AWS Amplify gives us nice libraries for the frontend
113. And it can automatica!y generate queries, mutations, subscriptions and types for us!
114. I give up! multi-cloud guru
115. But this is not a!!
116. AppSync supports caching and offline data synchronization
117. Ok, but how do you test it? multi-cloud guru
118. It depends on your approach. It's good to have end-to-end tests, but you can test your Lambda code or VTL templates in isolation.
119. You can also run the app loca!y using AWS Amplify
120. What if we need to use more complex architecture, i.e. CQRS multi-cloud guru
121. Mutation Event storage Subscription Query Read-only table EventBridge Business logic Business logic
122. Mutation Event storage Subscription Query Read-only table EventBridge Business logic Business logic
123. Mutation Event storage Subscription Query Read-only table EventBridge Business logic Business logic
124. multi-cloud guru
126. Serverless GraphQL Guru
128. Quick Summary: • GraphQL makes your frontend and backend connection effortless • AppSync makes GraphQL management effortless • Serverless GraphQL makes you a super hero
129. @slobodan_ vacationtracker.io