On: Anti-Patterns to Avoid in Lambda Based Apps

[BerislavLopac]

A variant of #1 that I've encountered has a single "service" with a multiple entry-point functions, being deployed as several lambda's - one per entry point - so each lambda contains a copy of the whole codebase.

[lormayna → BerislavLopac]

You can use a Lambda Layer and avoid repeating the same code: https://docs.aws.amazon.com/lambda/latest/dg/invocation-laye...

[WatchDog → BerislavLopac]

It addresses the least privilege issue, and maybe package size (depending how intelligent your build tooling is).