We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A lot of cons about Appsync are around VTL. With direct to lambda resolvers does that reduce the concern or did you find other issues? https://docs.aws.amazon.com/appsync/latest/devguide/resolver-mapping-template-reference-lambda.html#direct-lambda-resolvers
Scaling of websockets via subscriptions is a powerful feature to give up in the con section. Can rate limiting via WAF be sufficient?
Just curious the experience you had, not asking for any changes.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A lot of cons about Appsync are around VTL. With direct to lambda resolvers does that reduce the concern or did you find other issues? https://docs.aws.amazon.com/appsync/latest/devguide/resolver-mapping-template-reference-lambda.html#direct-lambda-resolvers
Scaling of websockets via subscriptions is a powerful feature to give up in the con section. Can rate limiting via WAF be sufficient?
Just curious the experience you had, not asking for any changes.
The text was updated successfully, but these errors were encountered: