Three municipal Lambdas share the same GIS SDK and logging library, and copying those zip dependencies into every function bloats packages. What should the team use?
Select an answer to reveal the explanation.
Short Explanation
One shared toolbox on the truck beats packing the same wrenches into three separate kits. A Lambda layer carries the common GIS SDK and logging library so each function zip stays lean. Duplicating zips, Glacier thaws on cold start, or pasting SDKs into source are the bloated paths.
Full Explanation
Lambda layers package shared libraries and runtimes that multiple functions can attach, reducing duplicated deployment size. Copying dependencies into every zip increases package bulk. Retrieving large libraries from Glacier on cold start adds latency and complexity. Inlining SDKs into handler source is unmaintainable.