AWS AppSync Reviews

Our company handles in-house projects and serves clients globally. My role with AppSync involves creating GraphQL APIs. There are different types of APIs, such as REST API, GraphQL API, and WebSockets, depending on the project's needs. GraphQL AWS is among the most crucial APIs we utilize across various products. In AppSync, I create diverse GraphQL APIs with various functions and schemas.

AWS has made it easy for developers like me to create and manage GraphQL APIs. The ease of use is a main advantage, allowing even beginners to start from scratch and learn through AppSync. 

Before AWS, developing and managing APIs was quite complex. AWS provided AppSync, which assists developers and startup founders. Startups blooming everywhere benefit from this service, welcoming those who lack prior knowledge. 

When working on AWS, I notice that Amazon regularly implements new features. For instance, with the Lambda service, AWS is transitioning from an old editor to a new one.

Similarly, AppSync frequently introduces updates and changes. This trend is making the user interface more accessible, even for individuals without a technical background.

Additionally, the cost is attractive, as AWS operates on a pay-as-you-go basis. These factors make AppSync both easy to use and cost-effective.

In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial. Regular updates might soon address this need. 

Currently, incorporating features like IAM roles and permissions during API creation is essential.

I have been working with AppSync for around five months.

Regarding performance, I haven't encountered issues in my current projects; however, I have heard others mention it. In most real-world cases, we don't predominantly use GraphQL. REST APIs and WebSockets are more common. At this point, I don't believe it's much of a concern.

On a rating of one to ten, I would say I find it scalable at around six or seven out of ten.

I have had experiences with AWS customer service, especially at the beginning of my career as a cloud editor. At one point, I reached out to the support team for assistance.

Neutral

I haven't worked with other cloud providers, however, within AWS, I have worked with various services.

The initial setup of AppSync is relatively straightforward. Upon opening AppSync, I encounter a list of APIs. For instance, when creating a GraphQL API, I'd select the API type, name it, assign permissions, and determine the region. 

It's crucial that the AppSync schema is error-free and well-prepared. Templates are vital too, enabling external programs to interact with the API. They define how data is translated and passed. 

Once the schema and data source configurations are set correctly and templates are configured for requests and responses, setting up the API linkage becomes routine. Knowledge of AWS cloud expedites this process to an hour or two. For complete beginners, familiarization might take five to six hours.

We initially had limited knowledge about AWS costs. As beginners, we ran many instances for over a month. Consequently, we received a bill from Amazon for around $20, which was unexpected. This highlights the importance of thorough understanding and learning before diving into AWS.

I recommend AppSync for other users, contingent on their project needs. Given that cloud technology is global, scalable, and user-friendly, AppSync is a beneficial choice. Previously, developing GraphQL APIs required manual effort, while Amazon has simplified this process. However, the choice between GraphQL and alternatives like WebSockets should depend on project requirements. While I advocate for AppSync, it should align with project goals. 

Overall, I would rate the product a seven out of ten.

We require our frontend and multiple frontends to communicate with the backend via GraphQL. GraphQL, provides a lot of flexibility in terms of data retrieval and data manipulation, allowing you to get exactly the data you need, nothing more, nothing less. 

We require our frontend, mobile or web frontend to communicate with the backend, and many other APIs through GraphQL. At that level, AppSync, like an API gateway, is capable of sourcing data from multiple data sources.

It can provide you with the GraphQL endpoint. As a result, you won't have to write any additional backend code. Transitioning from a server-based to a serverless architecture is relatively simple, and very fast.

It has the ability to connect to virtually any type of data source, whether it's a database, an API, or an old-school XML-based data source. 

Support for multiple data sources and formats is a fantastic feature.

I believe it is adequate, and I would say that it is a very innovative solution.

I would like to have the ability to run AppSync on-premises. It is entirely AWS at the moment. If you wanted to switch from AWS to Google Cloud or Azure, you can't. You are experiencing significant vendor lock-in.

Moving to other clouds is impossible without significantly rearchitecting your applications.

I have been working with AWS AppSync for six years.

We are working with the most recent version.

AWS AppSync is a stable solution.

Although AWS AppSync is scalable, it does have some performance limitations.

We don't have many users right now. It would be close to 100 users, which isn't too many. However, we will be launching our product very soon. We anticipate that the number of users will increase to a couple of hundred.

We did not need to contact AWS support. I am unable to comment. However, in general, AWS's technical support is excellent. So I'm not going to complain.

The initial setup is very straightforward.

The implementation was completed by an in-house team.

There is almost no maintenance. The developer's skillset alone needs to be good enough. It requires some expertise. Not everyone can use it without learning.

Licensing fees are paid on a monthly basis, and it is a pay-as-you-go model. Fees are paid per usage.

There are no fixed costs. They won't charge us anything if we don't use it.

People who are using other clouds will be unable to use them. However, it can be used by those with GraphQL. It is relevant to those considering serverless architecture. 

It is not a great fit for someone with a server-based backend they will find it difficult to adapt, and it will increase their maintenance overhead.

I would rate AWS AppSync a nine out of ten.