Amplify UI – Don't just prototype. Connect your UI to the cloud

Re:Amplify UI – Don't just prototype. Connect your UI to the... by picardo on Saturday July 09, 2022 @09:37AM (#32034969)

Biggest drawback for me was having to use VTL to write my resolvers. Normally, I wouldn't mind using a template language for UIs, but not for business logic. This isn't Amplify's fault. They use AppSync, which made the design decision to use VTL. Until AppSync adds support for TypeScript, I wouldn't consider using Amplify toolchain to start a new project.

As an aside, you can still use Lambda resolvers rather than pipeline resolvers, but that's tedious to set up and it's also more costly than pipeline resolvers.

[ Parent | on HN ]

Re:Amplify UI – Don't just prototype. Connect your UI to the... by swyx on Saturday July 09, 2022 @04:13PM (#32038847)

youre talking about appsync when the posted article is on amplify UI.. pretty far away from that specific service and ignores a lot of usecases which dont touch appsync

[ Parent | on HN ]

Re:Amplify UI – Don't just prototype. Connect your UI to the... by picardo on Saturday July 09, 2022 @04:39PM (#32039091)

I mentioned that AppSync is a different service but VTL is tightly integrated to Amplify workflow because of AppSync. If you use `amplify-cli` to generate your project, you get a folder full of VTL templates. The only way to modify the default behavior of your Amplify API is to override those templates. So I'd say it's very relevant.

[ Parent | on HN ]