swagger-api / swagger-api/swagger-codegen
Thoughts on a server for AWS API Gateway/Lambda
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
I'm wondering how the community would feel about a contribution of a new "server" type that is specific to deploying to AWS Lambda (Serverless architecture)?
While Lambda does make it quite simple to get started, going from a blank handler function to a full web service with routing/serialization of models, bindings to API Gateway, dependency injection, etc is a much larger task. All of this logic is boilerplate, except for the highly dynamic nature of the API definition itself.
If one follows an "API First" approach, Swagger CodeGen is a nice middleware that can glue together the boilerplate code with the customized nature of the API.
Given the fact that this would be a target for a vendor PaaS, I'm curious if the community here would be receptive to this addition.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is an exploratory proposal for a new server type targeting AWS Lambda and API Gateway; it names no files, tests, or entry points. Start by reviewing how Swagger CodeGen currently generates server stubs, then determine the scope and acceptance criteria for routing, model serialization, bindings, dependency injection, and dynamic API definitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100