Problem
The project currently targets traditional server deployments only, limiting deployment options for teams using serverless platforms (AWS Lambda, Google Cloud Functions).
Proposed Solution
Add serverless deployment support with:
- Mangum adapter integration for AWS Lambda
- Deployment configuration and handler entry point
- Documentation for serverless-specific considerations (cold starts, connection pooling, timeout limits)
- Example SAM/CDK template for infrastructure provisioning
Area
DevOps / CI/CD
Alternatives Considered
- Vercel deployment only (see #12): covers one platform but not general serverless support
- Container-based deployment (ECS/Fargate): heavier infrastructure, not truly serverless
Problem
The project currently targets traditional server deployments only, limiting deployment options for teams using serverless platforms (AWS Lambda, Google Cloud Functions).
Proposed Solution
Add serverless deployment support with:
Area
DevOps / CI/CD
Alternatives Considered