[service] [request] support parallel invocations on a single instance

Open
#97 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, node.js
Domain
backend, cloud

Research direction

No repository files, tests, or entry points are named; start by checking whether this roadmap repository contains implementation code for Lambda@Edge invocation handling. Done would mean defining and delivering support for multiple concurrent invocations on one instance, including the behavior and constraints needed for the stated authentication and CloudFront use case.

Written by the indexing model from the issue text.

Description

One of our highly used Node.js lambdas is mostly IO-bound, waiting for a HTTP request to complete. It would be nice if a single lambda instance can handle multiple invocations in parallel, so we can save on start-up cost, have some shared cache and not run into our quota limit as fast (we're capped at 2500 at the moment, but it's not enough).

We'd use a regular Node.js service for this, but in this case we're using Lambda@edge so we're in a bind.

The specific lambda as a auth/acl check in cloudfront before we hit a S3 origin.

Community Note
  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
What do you want us to build?

Which service(s) is this request for?
This could be AWS Lambda itself, or integrations with other services.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

Are you currently working around this issue?
How are you currently solving this problem?

Additional context
Anything else we should know?

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Dominant language
No language data
Stars
196
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-roadmap

All issues in aws/aws-lambda-roadmap

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.