Download to read offline
![GET https://myapp.com/user/1234
REST API
{
“id”: “1234”,
“firstName”: “Yan”,
“lastName”: “Cui”,
“dob”: “…”,
…
}
GraphQL API
POST https://myapp.com/graphql
{
getProfile (id: “1234”) {
friends {
firstName
lastName
}
}
}
{
“friends”: [{
“firstName”: “Gerard”,
“lastName”: “Sans”
}, {
“firstName”: “Ant”,
“lastName”: “Stanley”
}]
}](https://image.slidesharecdn.com/whyappsync-210211151515/85/Why-your-next-serverless-project-should-use-AWS-AppSync-15-320.jpg)
![type Mutation {
addPost(id: ID! author: String! title: String content: String url: String): Post!
}
type Subscription {
addedPost: Post
@aws_subscribe(mutations: [“addPost"])
}](https://image.slidesharecdn.com/whyappsync-210211151515/85/Why-your-next-serverless-project-should-use-AWS-AppSync-128-320.jpg)
![type Mutation {
addPost(id: ID! author: String! title: String content: String url: String): Post!
}
type Subscription {
addedPost: Post
@aws_subscribe(mutations: [“addPost"])
}](https://image.slidesharecdn.com/whyappsync-210211151515/85/Why-your-next-serverless-project-should-use-AWS-AppSync-129-320.jpg)
![type Mutation {
addPost(id: ID! author: String! title: String content: String url: String): Post!
}
type Subscription {
addedPost: Post
@aws_subscribe(mutations: [“addPost"])
}
subscriber
publisher
subscriber
subscriber](https://image.slidesharecdn.com/whyappsync-210211151515/85/Why-your-next-serverless-project-should-use-AWS-AppSync-130-320.jpg)
![type Mutation {
addPost(id: ID! author: String! title: String content: String url: String): Post!
}
type Subscription {
addedPost: Post
@aws_subscribe(mutations: [“addPost"])
}
publisher
subscriber
subscriber
subscriber](https://image.slidesharecdn.com/whyappsync-210211151515/85/Why-your-next-serverless-project-should-use-AWS-AppSync-131-320.jpg)
![type Mutation {
addPost(id: ID! author: String! title: String content: String url: String): Post!
}
type Subscription {
addedPost: Post
@aws_subscribe(mutations: [“addPost"])
}
publisher
subscriber
subscriber
subscriber](https://image.slidesharecdn.com/whyappsync-210211151515/85/Why-your-next-serverless-project-should-use-AWS-AppSync-132-320.jpg)
Uploaded byYan Cui
Why your next serverless project should use AWS AppSync
The document discusses the advantages of using AWS AppSync for serverless projects, highlighting its ability to efficiently manage GraphQL APIs and handle data from various sources like DynamoDB and RDS. It emphasizes features such as eliminating overfetching and underfetching problems, built-in monitoring, and flexibility in product iterations. AppSync also provides a user-friendly interface for real-time applications and offers easier integration compared to traditional API gateways.
More Related Content
Similar to Why your next serverless project should use AWS AppSync
Why your next serverless project should use AWS AppSync
- 1. Why your nextserverless project should use AWS AppSync
- 2. Yan Cui http://theburningmonk.com @theburningmonk Developer Advocate@ Independent Consultant AWS user since 2009 since 2018 yan@lumigo.io
- 3. Guy Moses @guymoses3 Software Engineer@ guy@lumigo.io
- 4.
- 5. Learn GraphQL andAppSync by building a Twitter clone with these technologies appsyncmasterclass.com
- 6.
- 7. A Query Languagefor your APIs and a runtime for fulfiling those queries with your existing data
- 8.
- 9.
- 10.
- 11.
- 12. schema server datasources DynamoDB RDS ElasticSearch AppSync
- 13. GET https://myapp.com/user/1234 REST API { “id”:“1234”, “firstName”: “Yan”, “lastName”: “Cui”, “dob”: “…”, … }
- 14. GET https://myapp.com/user/1234 REST API { “id”:“1234”, “firstName”: “Yan”, “lastName”: “Cui”, “dob”: “…”, … } GraphQL API POST https://myapp.com/graphql { getProfile (id: “1234”) { firstName lastName } } { “firstName”: “Yan”, “lastName”: “Cui” }
- 15. GET https://myapp.com/user/1234 REST API { “id”:“1234”, “firstName”: “Yan”, “lastName”: “Cui”, “dob”: “…”, … } GraphQL API POST https://myapp.com/graphql { getProfile (id: “1234”) { friends { firstName lastName } } } { “friends”: [{ “firstName”: “Gerard”, “lastName”: “Sans” }, { “firstName”: “Ant”, “lastName”: “Stanley” }] }
- 22. GET https://myapp.com/user/1234 REST API { “id”:“1234”, “firstName”: “Yan”, “lastName”: “Cui”, “dob”: “…”, … }
- 23. GET https://myapp.com/user/1234 REST API { “id”:“1234”, “firstName”: “Yan”, “lastName”: “Cui”, “dob”: “…”, … } Returns data we don’t need
- 24. GET https://myapp.com/user/1234 REST API { “id”:“1234”, “firstName”: “Yan”, “lastName”: “Cui”, “dob”: “…”, … } Returns data we don’t need Overfetching
- 25. GET https://myapp.com/user/1234 REST API { “id”:“1234”, “firstName”: “Yan”, “lastName”: “Cui”, “dob”: “…”, … } Doesn’t have everything we need
- 26. GET https://myapp.com/user/1234 REST API GEThttps://myapp.com/sports/football GET https://myapp.com/sports/squash … GET https://myapp.com/user/1234/activities
- 27. GET https://myapp.com/user/1234 REST API GEThttps://myapp.com/sports/football GET https://myapp.com/sports/squash … GET https://myapp.com/user/1234/activities
- 28. GET https://myapp.com/user/1234 REST API GEThttps://myapp.com/sports/football GET https://myapp.com/sports/squash … GET https://myapp.com/user/1234/activities Underfetching n+1 requests
- 29. BFFs (Backends forFrontends)
- 30.
- 31. BFF Need lots ofBFFs
- 32. BFF Need lots ofBFFs Duplicating work
- 33. GraphQL = nomore bespoke BFFs
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48. Solves problems ofoverfetching and underfetching
- 49. Strongly typed contractbetween client and server
- 50. Implement “joins” withDynamoDB effortlessly
- 51. Enables rapid productiterations on the frontend
- 52.
- 53. Fully managed GraphQLservice
- 54. query server datasources DynamoDB RDS ElasticSearch AppSync Lambda HTTP
- 55. AppSync supports 5data sources
- 56. AppSync supports 5data sources HTTP Put GraphQL in front of existing REST APIs
- 57. REST API 1 RESTAPI 2 REST API 3 REST API 4 existing UI page BFF
- 58. REST API 1 RESTAPI 2 REST API 3 REST API 4 existing UI page new UI page AppSync BFF
- 59. REST API 1 RESTAPI 2 REST API 3 REST API 4 existing UI page new UI page AppSync BFF
- 60. REST API 1 RESTAPI 2 REST API 3 REST API 4 existing UI page new UI page AppSync
- 61. REST API 1 RESTAPI 2 REST API 3 REST API 4 existing UI page new UI page AppSync DynamoDB
- 62. REST API 1 RESTAPI 2 REST API 3 existing UI page new UI page AppSync DynamoDB
- 63. AppSync supports 5data sources DynamoDB NoSQL High performance Infinite scale Semi-schema’d Simple queries
- 64. AppSync supports 5data sources DynamoDB RDS (Aurora Serverless) NoSQL High performance Infinite scale Semi-schema’d Simple queries Relational Database Complex queries
- 65. AppSync supports 5data sources DynamoDB RDS (Aurora Serverless) ElasticSearch NoSQL High performance Infinite scale Semi-schema’d Simple queries Relational Database Complex queries Search engine Full-text search
- 66. AppSync supports 5data sources DynamoDB RDS (Aurora Serverless) ElasticSearch NoSQL High performance Infinite scale Semi-schema’d Simple queries Relational Database Complex queries Search engine Full-text search Lambda Function as a Service Integrate with any other services
- 67. scalable & multi-azout of the box
- 68. pay as youuse ($4.00 per million Query/Mutation operations)
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 76. which resolver is theproblem?
- 84. NO SERVERS tomanage!
- 85. AppSync vs APIGateway
- 86. Fully managed GraphQLservice Caching Monitoring/Logging Websockets WAF
- 87. Fully managed GraphQLservice Caching Monitoring/Logging Websockets WAF Direct integration with Lambda/DynamoDB/RDS/ElasticSearch
- 88. Fully managed GraphQLservice Caching Monitoring/Logging Websockets WAF Direct integration with Lambda/DynamoDB/RDS/ElasticSearch auth: Cognito/AWS_IAM/API_KEY/OPENID_CONNECT
- 89. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF API Gateway
- 90. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF Direct integration with most AWS services API Gateway
- 91.
- 92. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF Direct integration with most AWS services auth: Cognito/AWS_IAM/API_KEY/OPENID_CONNECT/LAMBDA API Gateway
- 93. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF Direct integration with most AWS services auth: Cognito/AWS_IAM/API_KEY/OPENID_CONNECT/LAMBDA Custom domain names API Gateway
- 94. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF Direct integration with most AWS services auth: Cognito/AWS_IAM/API_KEY/OPENID_CONNECT/LAMBDA Custom domain names Private endpoints API Gateway
- 95. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF Direct integration with most AWS services auth: Cognito/AWS_IAM/API_KEY/OPENID_CONNECT/LAMBDA Custom domain names Private endpoints Resource policies API Gateway
- 96. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF Direct integration with most AWS services auth: Cognito/AWS_IAM/API_KEY/OPENID_CONNECT/LAMBDA Custom domain names Private endpoints Resource policies API Gateway
- 97. Fully managed servicefor REST and Websocket APIs Caching Monitoring/Logging Websockets WAF Direct integration with most AWS services auth: Cognito/AWS_IAM/API_KEY/OPENID_CONNECT/LAMBDA Custom domain names Private endpoints Resource policies API Gateway
- 98.
- 101. API Gateway hasno built-in group-based authentication
- 102. 1. Assign IAMrole to each group to control which endpoints a user can access How to implement group-based authentication in API Gateway
- 103. 1. Assign IAMrole to each group to control which endpoints a user can access 2. Assign precedence to each group How to implement group-based authentication in API Gateway
- 104. 1. Assign IAMrole to each group to control which endpoints a user can access 2. Assign precedence to each group 3. Use a Lambda authorizer to: How to implement group-based authentication in API Gateway
- 105. 1. Assign IAMrole to each group to control which endpoints a user can access 2. Assign precedence to each group 3. Use a Lambda authorizer to: 1. Verify user belongs to the Cognito user pool and fetch user’s details How to implement group-based authentication in API Gateway
- 106. 1. Assign IAMrole to each group to control which endpoints a user can access 2. Assign precedence to each group 3. Use a Lambda authorizer to: 1. Verify user belongs to the Cognito user pool and fetch user’s details 2. Pick a group based on precedence How to implement group-based authentication in API Gateway
- 107. 1. Assign IAMrole to each group to control which endpoints a user can access 2. Assign precedence to each group 3. Use a Lambda authorizer to: 1. Verify user belongs to the Cognito user pool and fetch user’s details 2. Pick a group based on precedence 3. Generate policy for user How to implement group-based authentication in API Gateway
- 108. 1. Assign IAMrole to each group to control which endpoints a user can access 2. Assign precedence to each group 3. Use a Lambda authorizer to: 1. Verify user belongs to the Cognito user pool and fetch user’s details 2. Pick a group based on precedence 3. Generate policy for user How to implement group-based authentication in API Gateway
- 109. How to implementgroup-based authentication in AppSync
- 110. API Gateway hasrequest validation but no response validation
- 112. Response validation helpsprevent data leaks
- 113. Security is asmuch about what your application SHOULD do as what it SHOULDN’T do
- 114. Request and Responsevalidation is built into GraphQL
- 116.
- 118.
- 119.
- 120.
- 121.
- 122.
- 123. low-level construct whereYOU have to manage connection mapping
- 124. no support forbroadcasts (e.g. broadcasting to a million connected users equates to fetching 1M items from DynamoDB and then make 1M API calls to API Gateway…)
- 125. fine for simpleuse cases
- 127. type Mutation { addPost(id:ID! author: String! title: String content: String url: String): Post! }
- 128. type Mutation { addPost(id:ID! author: String! title: String content: String url: String): Post! } type Subscription { addedPost: Post @aws_subscribe(mutations: [“addPost"]) }
- 129. type Mutation { addPost(id:ID! author: String! title: String content: String url: String): Post! } type Subscription { addedPost: Post @aws_subscribe(mutations: [“addPost"]) }
- 130. type Mutation { addPost(id:ID! author: String! title: String content: String url: String): Post! } type Subscription { addedPost: Post @aws_subscribe(mutations: [“addPost"]) } subscriber publisher subscriber subscriber
- 131. type Mutation { addPost(id:ID! author: String! title: String content: String url: String): Post! } type Subscription { addedPost: Post @aws_subscribe(mutations: [“addPost"]) } publisher subscriber subscriber subscriber
- 132. type Mutation { addPost(id:ID! author: String! title: String content: String url: String): Post! } type Subscription { addedPost: Post @aws_subscribe(mutations: [“addPost"]) } publisher subscriber subscriber subscriber
- 134. much easier touse, and can cater for more complex use cases
- 135.
- 136. You can alsouse API Gateway with AppSync
- 137. AppSync vs GraphQLin Lambda
- 138.
- 139.
- 140.
- 141.
- 142. What you need WhatAppSync offers
- 143. What you need WhatAppSync offers
- 144. What you need WhatAppSync offers What’s missing in AppSync
- 145. No custom scalartypes
- 146.
- 147. GraphQL scalar typesAppSync scalar types ID String Int Float Boolean AWSDate AWSTime AWSDateTime AWSTimestamp AWSEmail AWSJSON AWSURL AWSPhone AWSIPAddress
- 148. No custom scalartypes
- 151.
- 153. Service A Resolver AResolver B Resolver C graphql
- 154. Gateway Service A ServiceB Service C graphql graphql graphql graphql
- 155. Gateway Service A ServiceB Service C graphql graphql graphql graphql Resolver A Resolver B Resolver C Resolver D Resolver E
- 156. Client App AppSync AppSyncAppSync graphql graphql graphql
- 157. What you need WhatAppSync offers AppSync features you need to replicate
- 158. What you need WhatAppSync offers AppSync features you need to replicate Direct integration with DynamoDB
- 159. What you need WhatAppSync offers AppSync features you need to replicate Direct integration with DynamoDB Direct integration with ElasticSearch
- 160. What you need WhatAppSync offers AppSync features you need to replicate Direct integration with DynamoDB Direct integration with ElasticSearch Direct integration with RDS
- 161. What you need WhatAppSync offers AppSync features you need to replicate Direct integration with DynamoDB Direct integration with ElasticSearch Direct integration with RDS Direct integration with HTTP
- 162. What you need WhatAppSync offers AppSync features you need to replicate Direct integration with DynamoDB Direct integration with ElasticSearch Direct integration with RDS Direct integration with HTTP Caching
- 163. What you need WhatAppSync offers AppSync features you need to replicate Direct integration with DynamoDB Direct integration with ElasticSearch Direct integration with RDS Direct integration with HTTP Resolver logging Caching
- 164. What you need WhatAppSync offers AppSync features you need to replicate Direct integration with DynamoDB Direct integration with ElasticSearch Direct integration with RDS Direct integration with HTTP Caching Resolver logging Group-based auth with Cognito
- 165.
- 166.
- 167. Can add custommiddlewares
- 168.
- 169.
- 170. API Gateway Lambda Usageplans Lambda authorizer
- 171. API Gateway AppSync Usageplans Lambda authorizer
- 172. API Gateway Lambda Coldstarts
- 173. AppSync DynamoDB No Lambda.No cold starts.
- 174. AppSync Fewer dependencies. Cold startsfaster. Lambda
- 176.
- 177. AppSync features you needto replicate What’s missing in AppSync
- 178. Use AppSync ifyou can, until you can’t