Skip to content
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.

Batch mutations seem to create separate AWS Lambda invocations #397

Open
prm-dan opened this issue Jun 29, 2020 · 0 comments
Open

Batch mutations seem to create separate AWS Lambda invocations #397

prm-dan opened this issue Jun 29, 2020 · 0 comments

Comments

@prm-dan
Copy link

prm-dan commented Jun 29, 2020

Hi! I have an Apollo server running using Serverless on AWS Lambda. I'm sending a bunch of mutations in a single batch to the Lambda. I would expect only one Lambda invocation for the whole batch. I'm seeing >=1 Lambda invocation per mutation in the batch. Splitting each mutation into a separate Lambda will be expensive and less efficient.

mutation {
  create0: createEntity(input: { ... }) { ... },
  create1: createEntity(input: { ... }) { ... },
  ...
  createN: createEntity(input: { ... }) { ... },
}
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant