Hacker News new | ask | show | jobs
by huangbong 2891 days ago
Do you have to deal with cold starts on AppSync?
1 comments
chrisco255 2891 days ago
Not for VTL-based resolvers, as far as I can tell. I haven't run performance numbers to be sure, but it seems like the VTL resolvers run pretty fast.

If you need to do really complicated logic in your resolvers, though, you'll probably want to write a Lambda to back those particular resolvers.

So a GraphQL query's performance may vary depending on how many resolvers are involved and whether those are VTL or Lambda.

link
appwiz 2890 days ago
(AWS AppSync tech lead here)

Spot on! Some of the use cases for the VTL-based resolvers are to minimize cold start and latency due to network I/O for resolver invocation. I recommend that you start with the VTL resolvers if they are available for your data source and evaluate performance[1]. Switch to AWS Lambda only if you identify missing features or can't meet performance expectations.

Also, we've absolutely heard your feedback about VTL and this is a large area of investment for AppSync. One of the enhancements we launched today in the console is auto-complete in the VTL resolver editor. Let us know if it improves the editing experience.

Thanks for using AppSync - we are always excited to hear your feedback and use cases!

[1] AWS AppSync produces logs and detailed resolver execution metrics. More information at https://docs.aws.amazon.com/appsync/latest/devguide/monitori...

link