Integrate http4s WebSocket app with AWS Lambda API Gateway
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 195
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Similarly to our existing http4s integration which allows to deploy an HttpApp as handler of AWS Lambda API Gateway events, it would be useful to have an integration for deploying a WebSocket app. Integrating with http4s would make it seamless to move applications between serverless and server deployments.
However, one important question is how the lifecycle is managed i.e. does the same Lambda instance handle the entirety of a WebSocket connection? If so, then we can be stateful across events and implement the handler with Stream/Pipe. Otherwise, I'm not entirely certain what the API should look like.
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
Start by examining the existing http4s integration that deploys an HttpApp as an AWS Lambda API Gateway handler, then compare its entry points with the WebSocket app requirements. Resolve how Lambda instances manage a WebSocket connection and define the Stream/Pipe-facing API; done means the lifecycle and integration design are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, scala
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100