Great vid - also be great if you could do a video on Amplify Gen 2 using their custom model implementation in appSync and how to extend using custom field resolvers using CDK together with the default Amplify stack
Here, we have both the apps, UI & CDK using typescript so we can share the codegen generated types. But if use flutter, then we have to maintain types (generated by codegen) in dart as well as typescript. Right?
JS resolver can be used for any case or if you need something more complex then a lambda is used? I have an app in appsync but I only use lambda but thanks to you I am going to change when I use dynamoDb
Here is a all new starter repo that contains all the topics covered in this video and more! github.com/focusOtter/fullstack-nextjs-cdk-starter@@uncoolcoder
There are many simple JavaScript codes that are not supported in the resolver. Sometimes we need to use the resolver, but when the code is not supported, we move to Lambda functions.
Hey! Yea, there are still a couple: 1. Scalability: Lambda does an amazing job scaling due to being serverless, but AppSync VTL (better yet, JS resolvers) are not only serverless, but functionless. 2. Cost: Less Lambda functions means less services to manage and account for. 3. Observability: XRay and other observability tools can give a more consistent picture of what is happening.
Great vid - also be great if you could do a video on Amplify Gen 2 using their custom model implementation in appSync and how to extend using custom field resolvers using CDK together with the default Amplify stack
Latest video (and repo) with Clerk covers exactly that :)
Hi can i get an example for subscriptions ? Thanks in advance
Here, we have both the apps, UI & CDK using typescript so we can share the codegen generated types. But if use flutter, then we have to maintain types (generated by codegen) in dart as well as typescript. Right?
Yup, you got it!
you havent comitted anything in the repo?
JS resolver can be used for any case or if you need something more complex then a lambda is used? I have an app in appsync but I only use lambda but thanks to you I am going to change when I use dynamoDb
Hey Enrique! A good rule of thumb is if you need an external package from npm them a Lambda may be needed. Thanks for joining the stream!
Hi @focusotter, the repo doesn't contain all the files. Thank you very much for your videos!
Oh thanks for calling that out, I'll look into this today!
@@focusotter Thank you very much!
@@focusotter no backend files
Here is a all new starter repo that contains all the topics covered in this video and more! github.com/focusOtter/fullstack-nextjs-cdk-starter@@uncoolcoder
@@focusotter Thank you!
Can you have one resolver per Table instead of one resolver per query/mutation?
There are many simple JavaScript codes that are not supported in the resolver. Sometimes we need to use the resolver, but when the code is not supported, we move to Lambda functions.
Is there any advantage to using vtl vs using lambdas, besides cold start
Hey! Yea, there are still a couple:
1. Scalability: Lambda does an amazing job scaling due to being serverless, but AppSync VTL (better yet, JS resolvers) are not only serverless, but functionless.
2. Cost: Less Lambda functions means less services to manage and account for.
3. Observability: XRay and other observability tools can give a more consistent picture of what is happening.
Looks like AWS is moving away from VTL and recommend JS resolvers. Check out the VTL doc