aws / aws/aws-lambda-roadmap

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

オープン
#97 コメント 1 件 リアクション 1 件 担当者 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 の呼び出し処理を実装するコードが含まれているか確認してください。完了とは、1つのインスタンスで複数の同時呼び出しをサポートする機能を定義して提供することを意味し、提示された認証および CloudFront のユースケースに必要な動作と制約も含みます。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
aws, node.js
領域
backend, cloud
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
活発
明瞭さ
おおむね明確
初心者へのやさしさ
28/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。