aws / aws/aws-lambda-roadmap

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

未关闭
#97 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
没有语言数据
星标
196
派生
5
PR 合并指标
30 天内没有已合并 PR

描述

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](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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.)

贡献指南

打开贡献指南

调研方向

未指定仓库文件、测试或入口点;首先检查此路线图仓库是否包含用于处理 Lambda@Edge 调用的实现代码。完成意味着定义并交付对单个实例上的多个并发调用的支持,包括所述身份验证和 CloudFront 用例所需的行为与约束。

由索引模型根据 Issue 内容生成。

评估

技术栈
aws, node.js
领域
backend, cloud
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
活跃
描述清晰度
基本清楚
新手友好度
28/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。