Custom Lambda runtime?
Nobody has claimed this yet.
- #276 by @scott-thomson239 — closed without merging
- Dominant language
- Scala
- Stars
- 195
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Following from https://github.com/typelevel/feral/issues/132, @baccata points out that AWS offers a similarly low level interface to build a custom Lambda Runtime.
https://docs.aws.amazon.com/lambda/latest/dg/runtimes-custom.html
The advantage of implementing a custom runtime is the capability to process multiple events concurrently, but it's unclear if AWS supports this. On the one hand, polling for incoming events is completely within the lambda's control, and an id is used to pair responses with events so they don't necessarily need to be processed in order. But on the other, there are some strange assumptions such as the use of environment variables to pass around tracing headers, which makes me think this is unsupported behavior.
This should be further investigated.
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 with issue 132 and AWS's custom Lambda runtime documentation linked in the report. Investigate whether concurrent event processing is supported, including the concerns about polling, response IDs, and tracing headers; done means the support question is resolved and the implementation scope is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, scala
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100