2 ms·
Just for comparison, Amazon sees what is going on here -- explosion of 3rd party management frameworks for API Gateway & Lambda -- and wants to avoid fragmentat
by abalone 10y ago
Just for comparison, Amazon sees what is going on here -- explosion of 3rd party management frameworks for API Gateway & Lambda -- and wants to avoid fragmentation.
They're working on a thing called SAM which is built on CloudFormation: https://github.com/awslabs/serverless-application-model https://github.com/awslabs/serverless-application-model
More analysis here, which basically notes that SAM is more declarative in nature, and will likely push 3rd party frameworks to be more cross-platform and/or application-centric in focus: https://techbeacon.com/aws-open-sources-serverless-model-what-you-need-know https://techbeacon.com/aws-open-sources-serverless-model-wha...
- Prefinem 10y agoHaving started with Apex (http://apex.run/ http://apex.run/), used Serverless (https://serverless.com/ https://serverless.com/) and tried to work with SAM, I find the SAM is not nearly as easy to use or documented well enough (compared to Serverless) to be useful. On top of that, SAM feels more like a method of using CloudFormation to deploy Lambda Functions and setup API Gateway which means a lot steeper learning curve for people getting into Lambda. After reInvent, I was pretty excited about SAM because it seemed like a perfect system to integrate with the Code Build/Pipeline tools, but after spending a week on it and not getting anywhere, I couldn't really recommend it to anyone.
- lostcolony 10y agoI'd actually compare it more closely with Chalice. SAM is essentially an extension to Cloudformations, whereas Chalice is the equivalent to Serverless (but in Python, and not nearly as mature). https://github.com/awslabs/chalice https://github.com/awslabs/chalice