Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Lambda Makes Serverless Applications a Reality

techcrunch.com

Post reply on HN
Print view View original

1–10 of 55 posts

Re: AWS Lambda Makes Serverless Applications a Reality

#2

Post by sinatra »

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...

Re: AWS Lambda Makes Serverless Applications a Reality

#3

Post by posabsolute »

It's funny we tested lambda + Amazon gateway api this week at work.

It's awesome!.. Until you have to deal with the cold start issue. Our first call takes about 1.5 seconds; and then all other calls take about 50-80ms.

Your container stays in cache about 5-10 minutes unless it is called back, there are no guarantees.

This micro service is not called often and for us 1.5 seconds is never acceptable.

Re: AWS Lambda Makes Serverless Applications a Reality

#4

Post by toomuchtodo »

posabsolute wrote: post #3

It's funny we tested lambda + Amazon gateway api this week at work. It's awesome!.. Until you have to deal with the cold start issue. Our first call takes about 1.5 seconds; and then all other calls take about 50-80ms. Your container stays in cache about 5-10 minutes unless it is called back, there are no guarantees. This micro service is not called often and for us 1.5 seconds is never acceptable.

You could use a scheduled cron task in Lambda to make requests to keep your API hot.

Re: AWS Lambda Makes Serverless Applications a Reality

#5

Post by posabsolute »

toomuchtodo wrote: post #4
posabsolute wrote: post #3

It's funny we tested lambda + Amazon gateway api this week at work. It's awesome!.. Until you have to deal with the cold start issue. Our first call takes about 1.5 seconds; and then all other calls take about 50-80ms. Your container stays in cache about 5-10 minutes unless it is called back, there are no guarantees. This micro service is not called often and for us 1.5 seconds is never acceptable.

You could use a scheduled cron task in Lambda to make requests to keep your API hot.

Yeah we thought about that, but is it reliable? We were really not sure we could always get rid of the cold start issue.

Re: AWS Lambda Makes Serverless Applications a Reality

#7

Post by eistrati »

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...

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 solve sooner rather than later, because a lot of customers are complaining about it ;)

Re: AWS Lambda Makes Serverless Applications a Reality

#8

Post by dozy »

Been having fun playing with Lambda to power various Amazon Echo skills[1]. Definitely easier than having to deploy with something like Elastic Beanstalk, or even App Engine.

We're also using this at mParticle Inc. to allow anybody to add themselves as an integration[2]. The point being that Lambda is a super-easy way to write _some_ server logic, even if it only serves as a proxy to something more complex.

[1] https://developer.amazon.com/public/solutions/alexa/alexa-sk...

[2] https://github.com/mParticle/mparticle-sdk-java

Re: AWS Lambda Makes Serverless Applications a Reality

#9

Post by eistrati »

mikkom wrote: post #6

Serverless = using someone elses servers?

I like this explanation: https://www.quora.com/What-is-Serverless-Computing

Quote - Serverless doesn’t mean servers are no longer involved. It simply means that developers no longer have to think "that much" about them. Computing resources get used as services without having to manage around physical capacities or limits.

Post reply on HN