←back to thread

AWS Lambda Silent Crash – A Platform Failure, Not an Application Bug [pdf]

(lyons-den.com)
115 points nonfamous | 1 comments | 15 Jul 25 01:22 UTC | HN request time: 0s | source
Show context
ceejayoz ◴[15 Jul 25 02:42 UTC] No.44567373[source]▶
I saw this come up on /r/aws a few days back.

This response seemed illuminating:

https://www.reddit.com/r/aws/comments/1lxfblk/comment/n2qww9...

> Looking at (this section)[https://will-o.co/gf4St6hrhY.png], it seems like you're trying to queue up an asyncronous task and then return a response. But when a Lambda handler returns a response, that's the end of execution. You can't return an HTTP response and then do more work after that in the same execution; it's just not a capability of the platform. This is documented behavior: "Your function runs until the handler returns a response, exits, or times out". After you return the object with the message, execution will immediately stop even if other tasks had been queued up.

replies(2): >>44567415 #>>44567675 #
mcflubbins ◴[15 Jul 25 02:49 UTC] No.44567415[source]▶
If this is the case (it might very well be) I do at least find it odd that no one on AWS' side was able to explain this to them.
replies(6): >>44567446 #>>44567457 #>>44567464 #>>44567509 #>>44567669 #>>44569284 #
m3sta ◴[15 Jul 25 03:06 UTC] No.44567509[source]▶
AWS has a lot of employees. Many of them don't know AWS very well.
replies(2): >>44567698 #>>44567748 #
1. scarface_74 ◴[15 Jul 25 03:57 UTC] No.44567698[source]▶
No AWS employee knows “AWS well”. AWS has a huge surface area. If you work on one of the service teams - ie the team that maintains the different AWS services - you are very much unlikely to know the entire AWS surface area and be focused on your team and surrounding services.

It use to be the case if you were interviewing for an SDE position, you were specifically told not to mention specific AWS services in the system design rounds and speak of generic technologies.