How to configure several projects to use a single API
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
We are working on a large sized API with several resources and methods. In order to keep the size of the resulting Lambda function small, we want to break the overall API into smaller [Chalice] projects, but they are all part of the same API. Is there a way to configure each Chalice project to be part of a single API?
```
API
/resource1/* -> maps to Chalice project 1
/resource2/* -> maps to Chalice project 2
```
We are currently developing directly in Lambda and mapping the Lambda functions to each resource/method in the API. It would help us tremendously to use Chalice instead, but performance and cost are a key factor.
Thanks!
Contributor guide
Research direction
Start by reviewing Chalice's project configuration and its AWS Lambda/API Gateway deployment flow, using the issue's split-resource example as the target behavior. Done means establishing whether several Chalice projects can map their resources into one API while keeping separate Lambda functions, and documenting the required configuration or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100