Thanks for the great writeup! I wanted to expand on some of the limitations you mentioned:
Lambda Function Code Must Still Be Written: This is the case with any serverless framework or service and is by design. Even if you're following a tutorial with sample code, you'll still need to modify it to fit your needs. The beauty of serverless is that it does everything except write your code for you, so you can focus on your unique business logic.
Code Must Still Be Copied and Pasted: If you're working in connected mode, changes are saved to a local template file, and then you can use the SAM CLI to deploy from your machine - no copy/pasting needed!
Not Suitable for Complicated Use Cases: While we're working on expanding resource support, you can actually open an existing CFN or SAM template and visualize it - even incredibly complex ones!
I am Govind, a seasoned Cloud Architect with extensive experience in delivering complex migration projects. With my 11x AWS Certifications, I am well-equipped to tackle any challenge that comes my way
Thanks for the great writeup! I wanted to expand on some of the limitations you mentioned:
Lambda Function Code Must Still Be Written: This is the case with any serverless framework or service and is by design. Even if you're following a tutorial with sample code, you'll still need to modify it to fit your needs. The beauty of serverless is that it does everything except write your code for you, so you can focus on your unique business logic.
Code Must Still Be Copied and Pasted: If you're working in connected mode, changes are saved to a local template file, and then you can use the SAM CLI to deploy from your machine - no copy/pasting needed!
Not Suitable for Complicated Use Cases: While we're working on expanding resource support, you can actually open an existing CFN or SAM template and visualize it - even incredibly complex ones!
Thanks @annaspies! So kind of you in helping out on and extending the capabilities with additional pointers.