AWS Lambda missing framework guidance and bundle size limitations
6/10 MediumDevelopers often start Lambda projects without frameworks, forcing manual setup of API Gateway and CloudWatch integrations. As architectures grow, the 50MB default deployment size limit becomes a constraint, requiring webpack bundling per function to stay under limits and improve deployment speed.
Sources
Collection History
The query engine binary is about 13MB, which increases your deployment bundle size and adds to cold start times. On AWS Lambda with a cold start, I measured about 300-500 milliseconds of additional latency from Prisma initialization.
One of the biggest mistakes made when creating a serverless architecture using AWS Lambda is writing functions without a framework. When starting out with AWS Lambda large bundle sizes aren't typically a problem, however when your architecture grows and you start to amass a large number of Lambda functions max bundle size starts to become an issue. There is a default deployment size limit of 50MB.