Blog Post: Two Views of Lambda Diverged in a Yellow Wood
category: AWS Serverless
The root of this divergence of understanding comes down to how Lambda was originally positioned. It started out as a service that was defined by its restrictions; only certain languages were permitted, you could only have a certain runtime per function, cold starts were a serious problem, you could only allocate so much RAM per function, and so on.
Over time, these restrictions started being relaxed and the service expanded. So, a lot of those early understandings of the platform became rapidly out of date.