Allow the SnsTemplate to support the SnsAsyncClient over the SnsClient (sync)

[jonathanmdr]

Type: Feature

Is your feature request related to a problem? Please describe.
Actually, the SnsTemplate uses a sync client to send events; the sync approach can cause some errors, such as software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: executor not accepting a task when the volume of events sent by the SnsTemplate is very high.

Describe the solution you'd like
Change the SnsTemple to use the async client approach similar to the SqsTemplate.

Describe alternatives you've considered
Allow a custom configuration for SnsTemplate to use the async client approach over the sync client.

Additional context

[MatejNedic]

Hey @jonathanmdr ,

Thanks on opening this issue.
We already have the same request for async SnsTemplate.

Issue is we have to define how are we going to do Async (possible even reactive Mono/Flux) Templates and Sync in same project.
This is ongoing topic we have been discussing but we plan to address it soon.

What I will implement in a next release (already have POC) is SNS batching:
https://docs.aws.amazon.com/sns/latest/dg/sns-batch-api-actions.html Amazon SNS message batching - Amazon Simple Notification Service

I hope this will be mitigation for you till we rethink how we want to do sync and async implementations and have autoconfiguration work with both.

If we change to async we are introducing breaking change and I am not in favour of that. I want to build from scratch fully async implementation.

[jonathanmdr]

Hello @MatejNedic,

If we change to async we are introducing breaking change and I am not in favour of that. I want to build from scratch fully async implementation.

I totally agree with you, a new implementation fully async is the better approach.