feat(large-messages): Add function interface for Large Messages Utility

[phipag]

Summary

This PR introduces an AspectJ-free function API for the Large Messages utility. Instead of annotation a method with @LargeMessage the following code can be written (example together with batch processing):

public class SqsBatchHandler implements RequestHandler<SQSEvent, SQSBatchResponse> {
    private final BatchMessageHandler<SQSEvent, SQSBatchResponse> handler;

    public SqsBatchHandler() {
        handler = new BatchMessageHandlerBuilder()
                .withSqsBatchHandler()
                .buildWithRawMessageHandler(this::processMessage);
    }

    @Override
    public SQSBatchResponse handleRequest(SQSEvent sqsEvent, Context context) {
        return handler.processBatch(sqsEvent, context);
    }

    private void processMessage(SQSEvent.SQSMessage sqsMessage) {
        LargeMessages.processLargeMessage(sqsMessage, this::handleProcessedMessage);
    }

    private void handleProcessedMessage(SQSEvent.SQSMessage processedMessage) {
        // processedMessage.getBody() will contain the content of the S3 Object
        // do something with the message
    }
}

This API is thread-safe.

For multi-parameter methods, the following simple pattern can be used:

public void handleRequest(SQSEvent event, Context context) {
    event.getRecords().forEach(message ->
        LargeMessages.processLargeMessage(message, processedMsg -> processMessage(processedMsg, context))
    );
}

It is important to note that the utility modifies the SQSMessage in-place to avoid duplicating large blobs in-memory.

Changes

To the reviewers: Ignore PMD findings regarding "Throwable" or "unused parameters". This is expected.

• Throwable needs to be catched for AspectJ compatibility
• Unused parameters is a unit test where the goal is to test this

Issue number: #2212

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud