Home > Net >  What are the limitations of using AWS appsync api(GraphQL) through Amplify?
What are the limitations of using AWS appsync api(GraphQL) through Amplify?

Time:09-06

I just want to avoid use of custom/manual resolvers in appsync completely. So I'm using Amplify to setup GraphQL appsync API in my app. I'm doing all the stuffs by changing schema.graphql and amplify push.

I have 2 questions :

1. What are the limitations and what problems I'm going to face in future?

2. Can graphql subscriptions get update when app is not running(like user should be notified)?

CodePudding user response:

  1. tons of business logic will be exposed on the client side code.
  2. I think for push notifications you would still have to go via external integrations like FCM/APNS. Multiple integration options are available in SNS

CodePudding user response:

Just to preamble these answers, the fact that you use an amplify generated schema and resolver doesn't stop you from later including custom resolvers and pipeline functions - it's just that you need to learn quite a bit about where to include them in the backend file structure of amplify.

1. What are the limitations and what problems I'm going to face in future?

This depends on how well your applications use-case matches the graphQL schema design and if your application is relatively self-contained. Amplify becomes more complex when your application needs to talk to other back-end systems, you'll need to start using DynamoDB triggers to notify other state machines/event bridge/SNS or similar services.

As mentioned none of these problems are crippling, you can deal with them later but it will be a step up in the AWS knowledge required to implement them.

2. Can graphql subscriptions get update when app is not running(like user should be notified)?

No. Anurag mentions SNS which would be a good option to out-app notify users, best to blend subscriptions and another service.

  • Related