Skip to content

Latest commit

 

History

History
29 lines (19 loc) · 849 Bytes

README.md

File metadata and controls

29 lines (19 loc) · 849 Bytes

lambda-mono

In this architecture, all artifacts (including static assets) are uploaded to a single Lambda, and all requests are handled by that Lambda.

architecture

Pros

  • Fast deploy
  • Easy to debug, logging, trace

Cons

  • Poor scaling

Important

Since a single Lambda handles all requests involving static assets, you are likely to hit concurrency limits. (HTTP 429 Error)
Enabling CloudFront alleviates this issue, but is not recommended for production use.

Example use case

  • Test
  • Development

Note

  • Lambda IAM authentication is unavailable when enable CloudFront
  • CloudFront caches only client assets (/_app/*).
  • The total file size must be less than the Lambda package size limit (50MB: Zipped, 250MB: Unzipped). (Including client assets, server scripts, and pre-rendered pages)