Nice article - just a couple of corrections. The maximum time for a lambda execution is 15 minutes, not 5.
Also, there are more observability solution options than listed (I understand this is written by Dashbird!). Not mentioned are Thundra APM, Espagon and Lumigo.
Agree with Ross, also there's x-ray too (aws native observability tool).
I'm not sure the cold starts timing are accurate/correct - possibly early versions of Lambda when running Java had cold start times of 1 - 2 seconds, but certainly I don't think its as bad as that now, this is all I can find on the interweb mikhail.io/serverless/coldstarts/a... - there are also other ways to improve cold start latency as documented here: aws.amazon.com/blogs/compute/opera....
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice article - just a couple of corrections. The maximum time for a lambda execution is 15 minutes, not 5.
Also, there are more observability solution options than listed (I understand this is written by Dashbird!). Not mentioned are Thundra APM, Espagon and Lumigo.
Agree with Ross, also there's x-ray too (aws native observability tool).
I'm not sure the cold starts timing are accurate/correct - possibly early versions of Lambda when running Java had cold start times of 1 - 2 seconds, but certainly I don't think its as bad as that now, this is all I can find on the interweb mikhail.io/serverless/coldstarts/a... - there are also other ways to improve cold start latency as documented here: aws.amazon.com/blogs/compute/opera....