This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture.
Normally, it takes a lot of work to scale a GraphQL API -- especially in an enterprise environment. With AWS AppSync, we've been able to significantly reduce the amount of work required to scale our GraphQL API. Similar to Lamda, AppSync takes literally minutes to set up. Almost immediately, you have a production ready API to interface with yourdisparate services (such as DynamoDB and Lambda). Of course, you basically need to commit to the AWS ecosystem... but if you do, then AppSync is a no-brainer. We've wasted so much time in the past setting up GraphQL infrastructure, but not any longer -- give it a try. Review collected by and hosted on G2.com.
By far, the thing I dislike the most is thr cost per request. Like AWS Lamda, if you're not careful, then your monthly AppSync bill can grow out of control. Of course, this only applies when your handling millions of requests per month. If you can keep your requests under a few million per month, the cost isn't very high.
The nerve wracking part is that, if there's an unexpected flurry of API requests, your bill can grow completely unexpectedly. I've seen this before in environments where an automatic retry was issued every few seconds. This led to millions of extra requests per month. Fortunately, AWS has great customer support, and can forgive certain instances like this. Bit it's important to be careful. Review collected by and hosted on G2.com.
Validated through a business email account
This reviewer was offered a nominal gift card as thank you for completing this review.
Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review.





