Skip to content

Conversation

gabrielcolson
Copy link

"The batch processing utility handles partial failures when processing batches from Amazon SQS, Amazon Kinesis Data Streams, and Amazon DynamoDB Streams."

I ported a basic implementation of @aws-lambda-powertools/batch to Effect without using it as a peer dependencies. The Processor is provided as a Layer and we could easily add new processors (like SQS FIFO) or let the user provide a custom one.

Questions

  • As we do not have a peer dependencies on @aws-lambda-powertools/batch, maybe this package could simply be called @effect-aws/batch?
  • How should we handle defects like Effect.die ? With the current implementation, the processing stops at the first defect and is never handled

Copy link

changeset-bot bot commented Sep 3, 2025

⚠️ No Changeset found

Latest commit: df4cbf6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant