I love the idea of eliminating the compute layer when lambda is doing very little; it just feels cleaner. However, I'm not yet as comfortable writing/managing VTL as I am writing a dead-simple lambda function. I suspect I'm not alone in that sentiment, but can't wait to give this a try.
API Gateway Service proxies offer an interesting value proposition, especially now that API Gateways offers a more affordable/streamlined HTTP API offering (API Gateway v2). Nevertheless, a cool tool to add to the toolbox!
Yeah, common to feel that way toward VLT. Still, I encourage you to spend some time in that space, esp. as it will make working with AWS Step Functions that much easier. I have found the VLT docs themselves to offer nicer coverage of the topic than the AWS docs. LOL, but I do have to occasionally say to myself "it's just a templating tool" to stay focused. Good luck.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Fantastic content, thanks for writing this up!
I love the idea of eliminating the compute layer when lambda is doing very little; it just feels cleaner. However, I'm not yet as comfortable writing/managing VTL as I am writing a dead-simple lambda function. I suspect I'm not alone in that sentiment, but can't wait to give this a try.
API Gateway Service proxies offer an interesting value proposition, especially now that API Gateways offers a more affordable/streamlined HTTP API offering (API Gateway v2). Nevertheless, a cool tool to add to the toolbox!
Yeah, common to feel that way toward VLT. Still, I encourage you to spend some time in that space, esp. as it will make working with AWS Step Functions that much easier. I have found the VLT docs themselves to offer nicer coverage of the topic than the AWS docs. LOL, but I do have to occasionally say to myself "it's just a templating tool" to stay focused. Good luck.