Code splitting - one project to n functions
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Maybe its already in place but is it possible to generate multiple lambda/function artifacts for a single ktor DSL based project by splitting it per route? Kotless could automatically create and manage API gateway routes pointing to individual lambdas based on the routes defined in the DSL.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the Ktor DSL routes are converted into deployment artifacts and how API Gateway routes are managed. Investigate whether one project can produce separate Lambda artifacts per route without breaking existing deployment behavior. Done means the project reliably creates and manages the expected functions and corresponding API Gateway routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kotlin
- Domain
- backend-api-design, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100