DEV Community

Introduction to AWS Lambda

Sagar on September 09, 2018

As we know things are changing so fast. Most enterprise companies are focusing on on-demand services or pay as you go services. Companies don't wan...

Read full post

Cristian Popescu • Sep 9 '18

Hello,

Great pointers, I always trust an opinion of someone using a technology, rather than of the ones building the technology.

In my case using AWS Lambda was not a big hassle since I was able to generate a small maven project with the use of sam-cli and go from there. I found that really useful since I did not work with AWS Lambda before. This can be considered in my opinion an advantage, and that is the tooling provided with the use of sam-cli and aws-cli together.

I was able to run everything locally and run the lambda with the cli tool.

One issue to note was the lack of ability to startup the dynamodb instance without starting up a docker image or starting it up manually.

That was actually the first time working with AWS Lambdas, hope I will get the chance again and bring more arguments.

Sagar • Sep 10 '18 • Edited

Hi Cristian, If we use serverless framework it will reduce headache of deploying code to cloud

Lewis Cowles • Sep 11 '18

Simply put it's too opaque. You need to be able to rationalize about it and it uses some janky ass magic which is great for beginners and leaves you stranded past that.

They need to work with open technologies to launch a new V3 which has the benefits (more than just HTTP triggers), and then it'll be easier to reason about.

I see greatest potential in OpenFaaS Framework for FaaS serverless workloads because it's open, and although I need to learn more about some of the tech (Kubernetes, Grafana) I know how to work with most of it and have a good conceptual model of how to graft it to multiple clouds.