AWS Lambda Makes Serverless Applications a Reality • Hacker News Board

Re: AWS Lambda Makes Serverless Applications a Reality

#51

Post by eistrati » Wed, Nov 25, 2015, 2:23 PM UTC

smt88 wrote: post #15

eistrati wrote: post #7

Earlier quoted context omitted.

Depends on your use case and what language you are currently using. We are using nodejs and have built our own collection of libraries: https://github.com/MitocGroup/deep-framework And here is an example: https://github.com/MitocGroup/deep-microservices-todo-app Based on our experience, currently AWS Lambda is amazing for data / content / asset management use cases. Cold start is a known issue, which I hope AWS will…

How is the 0.10.x version of Node treating you? That's what's keeping me off of Lambda at the moment. I guess I could use Babel before deployment, but what about external libs? I'm thinking of the following workflow: 1. Write/debug with TypeScript -> ES6 on Node 5 2. Compile to a single file (not sure if I can use tsc or Babel for this -- basically just inline all the imports) 3. Transpile the resulting single file t…

Here is a practical approach, how we do it:

1. We write everything in ES6, following code styling from Airbnb - https://github.com/MitocGroup/javascript

2. Every Lambda is separate npm package, therefore npm is managing all the dependencies; We include node_modules folder into the .zip file and upload it to AWS

3. Using Babel, transpile ES6 to ES5 - https://github.com/MitocGroup/deep-microservices-todo-app/bl...

4. To support 0.10.x, we're requiring Babel Polyfill - https://github.com/MitocGroup/deep-microservices-todo-app/bl...

As anticipated, the performance is not the best one, but functional for some of our use cases where time is not a constrain. That's why the combination with Amazon ECS is perfect complimentary match when AWS Lambda doesn't perform well, as required by the application.

Re: AWS Lambda Makes Serverless Applications a Reality

#52

Post by robterrell » Wed, Nov 25, 2015, 5:31 PM UTC

epoch1970 wrote: post #24

How does one version control the scripts and easily deploy them? How does one test them on one's own computer when developing them? Must the scripts be uploaded into AWS after every change if testing is to be done?

I spent my last week figuring this out. I tried several of the open source packages mentioned above including jaws and node-lambda. In the end, I use node-lambda for local testing. If you configure your package.json file correctly you can get VS Code to run and debug, which was a life-changer for me. However, "node-lambda deploy" was breaking something between the API Gateway and Lambda, so eventually I switched to using a package.json deploy script that uses the AWS command line to zip & upload the working directory.

Re: AWS Lambda Makes Serverless Applications a Reality

#53

Post by robterrell » Wed, Nov 25, 2015, 5:33 PM UTC

teej wrote: post #14

sinatra wrote: post #2

We're considering using API Gateway and Lambda for our upcoming API service. Would love to hear feedback from anyone who's tried it. From the linked article, I got one gist [1] which wasn't very favorable for the API Gateway + Lambda setup. [1] https://gist.githubusercontent.com/mpdehaan/d979252b9c69cfd1...

I'm so glad you asked this! I just built a service on API Gateway + Lambda in the past two weeks. Here's my unstructured thoughts - * I love that I don't have to provision any resources. The fact it will scale to volume automatically is a huge win. * Lambda was a treat to work with. We used it with Python. Both the web console and API interface worked great for us. * I was able to get Lambda development working end-t…

I could have just written this comment -- I spent the past two weeks doing the same thing, but in JS, and hit all of the same problems. In the end, I think API Gateway is more trouble than it's worth. I wish Lambda could have an exposed HTTP endpoint. Mapping all of the arguments in and out is so incredibly tedious when developing and things are changing fast.

Re: AWS Lambda Makes Serverless Applications a Reality

#54

Post by smt88 » Sat, Nov 28, 2015, 8:37 PM UTC

eistrati wrote: post #51

smt88 wrote: post #15

Earlier quoted context omitted.

How is the 0.10.x version of Node treating you? That's what's keeping me off of Lambda at the moment. I guess I could use Babel before deployment, but what about external libs? I'm thinking of the following workflow: 1. Write/debug with TypeScript -> ES6 on Node 5 2. Compile to a single file (not sure if I can use tsc or Babel for this -- basically just inline all the imports) 3. Transpile the resulting single file t…

Here is a practical approach, how we do it: 1. We write everything in ES6, following code styling from Airbnb - https://github.com/MitocGroup/javascript 2. Every Lambda is separate npm package, therefore npm is managing all the dependencies; We include node_modules folder into the .zip file and upload it to AWS 3. Using Babel, transpile ES6 to ES5 - https://github.com/MitocGroup/deep-microservices-todo-app/bl... 4. T…

Thanks so much for posting this! I was really curious and found this to be helpful.

Re: AWS Lambda Makes Serverless Applications a Reality

#55

Post by spullara » Tue, Dec 01, 2015, 2:04 AM UTC

twagner wrote: post #31

yeukhon wrote: post #12

If Lambda is able to expand the /tmp disk space from 500MB to a few GB I think that will further make the adopter better on my end. I have a requirement in which Lambda is a perfect solution except the disk space is not enough. Of course I can further divide the work into smaller chunks. If you have use distributed task library like Celery, just think of that no longer tie to your application, and you can run on even…

Appreciate the feedback/suggestions! We'll take a look at expanding the disk space, probably as part of the "power level" adjustment that already affects memory, CPU power, etc.

Why can't I access EFS? That seems like the best solution to this.