[xenomachina]

(I'm not the one you were replying to, FWIW)

> What about using Serverless or a framwork for Lambda stuff?

If you're using other parts of AWS than Lambda, is there a benefit to using serverless? If I still need to know aws cli for the other services I use, what's the point in learning a specialized tool that only works for one service?

[nickthemagicman]

Its your call. I like Serverless because it configures all the infrastructure for me, and keeps my lambda code super organized and in an immediately understandable framework.

Its like you COULD just use Ruby to code a site but all the power of Rails adds so much to it!

[xenomachina]

When I (briefly) looked at serverless it I thought it was a wrapper around just Lambda (and other Lambda-like services), but it sounds like it actually let you configure other types of AWS services. Are there any AWS services it doesn't work with?

That said, I'm not seeing how serverless is any more "immediately understandable" than Lambda. The serverless.yml files I'm finding when looking at examples seem about as complex as aws cli commands.

[nickthemagicman]

Read over the docs a little more. There's a reason it exists, has been around for years, and is widely used by many companies.

[jklein11]

Its less overhead. You don't have to worry about keeping the EC2 instance or web server running/patched/updated/etc. The juice may not worth the squeeze with the extra complexity of using AWS Lambda.

[xenomachina]

Are you comparing Lambda to non-Lambda, or are you saying that in addition to managing a Lambda function, serverless can also "[keep an] EC2 instance or web server running/patched/updated/etc"?