Feature request: simplify BatchProcessor by merging async and sync processing functions into one class

[am29d]

Use case

During the implementation of the Batch utility we heavily leaned into the Powertools python implementation and create two classes AsyncBatchProcessor and BatchProcessor. After the refactoring in #1677 we realised that we can implement process and processSync functions in one class.

Solution/User Experience

Create one class with two method for async processing as default and sync processing with sync suffix:

class BatchProcessor extends BasePartialBatchProcessor {
  public async processRecord(
    record: BaseRecord
  ): Promise<SuccessResponse | FailureResponse> {
 
  }

  /**
   * Process a record with instance's handler
   * @param _record Batch record to be processed
   * @returns response of success or failure
   */
  public processRecordSync(
    _record: BaseRecord
  ): SuccessResponse | FailureResponse {
  }
}

Alternative solutions

No response

Acknowledgment

• This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[am29d]

We have decided to leave the current implementation to let the developer make an explicit choice when to use sync and async batch processors. Otherwise we would have cases where we can register an async function and call sync processing and vice versa. This might lead to lack of information why certain functions failed during runtime.

By having explicit classes the developer would start with the core assumption what type of function they use for the batch processing.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.