AWS AppSync Reviews & Product Details

AWS AppSync comes with well-optimized solutions for data aggregation from various sources and exposure it as a GraphQL API. In that row, my favorite part of AppSync is it gives a massive jump on the performance increment compares to any other similar solution. When it comes to the AWS ecosystem it works much more effectively especially with lambda, DocumentDb, RDS, & Dynamodb. Review collected by and hosted on G2.com.

I don't see any major drawbacks or blockers when using AppSync, So I don't have many complaints about it. Anyhow, I feel like usage of this might hold our solutions more into the AWS ecosystem. Review collected by and hosted on G2.com.

The ease of development and testing that AWS provides is spectacular. One can get a prototype out the door quickly and efficiently and then move onto testing in rapid order. Review collected by and hosted on G2.com.

Long-running queries force one to go down the session workaround in order to get everything to work as expected. However, that is a pretty simple task and an understandable limitation. Review collected by and hosted on G2.com.

AWS AppSync makes creating a GraphQL API server (using an existing schema/creating one through the wizard) such a breeze that it can be in a couple of mins.

It provides a single pane of glass (API server) abstracting the data from multiple AWS Products like ElasticSearch, DynamoDB. It gives the flexibility to change the backends without impacting the API contract.

Any application (iOS/Android/Javascript) can be integrated with AppSync easily using AWS Amplify CLI

The editor it provides is a good playground for trying out the queries and supports good auto-completion, and can browse through the GraphQL schema for reference. Review collected by and hosted on G2.com.

Haven't seen any down sides yet but feel the learning curve is more considering it requires to be familar with other AWS database services for integrating with AppSync. Review collected by and hosted on G2.com.

AWS appsync enables the creation of API to access and combine heterogeneous databases. Multiple data sources could be supported using the API. The API can also access real time datasets involving unstructured, semi-structured or relational datasets. The ability to get connected with mobile devices and web services is a commendable feature. Local data access is provided when the device is offline and is automatically synced up when the device is back online. Also, it supports real-time subscriptions. Review collected by and hosted on G2.com.

The Appsync feature is pricey. The distributed dataset, when accessed, could be challenging to comprehend. GraphQL feature needs some deep exploration to understand the usage. The caching algorithm is not straightforward feature. Review collected by and hosted on G2.com.

App Sync combines data from databases, APIs, and other backend systems into a single GraphQL endpoint. Review collected by and hosted on G2.com.

User must have knowledge of data sources that app Sync is going to combine. There a learning curve involved. Debugging can be challenging if app Sync is not configured properly. Review collected by and hosted on G2.com.

AppSync, paired with AWS Amplify, allows you to create and iterate a scalable backend solution very quickly. While using this in an Amplify-powered project, we were able to pivot multiple times while still using the same codebase and same architecture patterns. AppSync's authentication options with Cognito (user & group-based access control), IAM (for accessing AppSync from other AWS resources), and API key access (for unauthenticated users to access data) is perhaps the most powerful feature. Review collected by and hosted on G2.com.

There's a few key downsides to be aware of before committing to AppSync. There is a compiled schema size limit of 64KB, which is not very much space if you want to have granular security permissions. If you aren't familiar with graphql, it may also be difficult to wrap your head around some of the access patterns, and because of some key limitations in dynamoDB there are some typical access patterns and queries that can be difficult (specifically, constucting simple M2M and 121 queries). The only substantial issues I have run into ended up being in my lack of understanding in how it functions. AppSync is in use in production for a multi tenant application, with complicated and granular user and group based access controls. Review collected by and hosted on G2.com.

AppSync is extremely useful and reliable GraphAPI and it handles the security aspect as well. It ensures users are correctly calling the API and handles error cases really well. Review collected by and hosted on G2.com.

It could be a little chaotic in its features and continuous references to documentation are necessary. It is sometimes also prone to hanging and indefinitely becoming non responsive. Review collected by and hosted on G2.com.

The most thing I like in AWS AppSync is it makes me able to create GraphQl API Services and it only takes a few minutes to create it.

I can view all data from all AWS services from one API server. Review collected by and hosted on G2.com.

Actually, I have nothing to dislike regarding this product.

for me, it's very useful and makes me very satisfied. Review collected by and hosted on G2.com.

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.

AWS AppSync has well-optimized data aggregation solutions from various sources and exposes it as a GraphQL API. AWS AppSync is available on AWS. One of the best things about AppSync is how much better it performs when compared to other similar solutions in that row. Review collected by and hosted on G2.com.

AppSync doesn't appear to have any major drawbacks or obstacles in my opinion, so I have no issues with it. As a result of this, I believe that using it will further integrate our products into the AWS ecosystem. Review collected by and hosted on G2.com.