Hacker News Reader

Can you share some more details about what you're trying to do with us? There's a latency floor when using the API Gateway of about 200 ms, which is unacceptable for a lot of APIs, but other than that we largely haven't been running into the issues you're dealing with. And if Meetup is any indication, AWS seems really invested in Lambda. (In terms of cost, it really would depend on what you're using it for.)

View on HN

well I built a user authentication and it takes 5~6 seconds for a real simple operation. it happens randomly and no way to debug it.

the opacity of being able to peer at what's going on in the backend is a real problem with AWS Lambda. I think that this lack of insight is going to bite down the road. Even now, I'm getting 'service error' with NO EXPLANATION what happened.

No offense, but this sounds exactly like the experience I had, and many friends had, before we actually learned how to use the service. If I had to guess, you're using the smallest possible 128MB config and not calling it very often. This presents a maximally-bad first experience for devs by Amazon but is not reflective of how it works once you get some actual utilization happening. All that said I moved to containers on Azure for unrelated reasons. But Lambda works fine (within its obvious architectural restrictions) and they'll hold your hand for a $49/month developer service plan fee.

Reply on news.ycombinator.com