-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for event externalization into AWS SNS and SQS #344
Comments
That's a great idea! I unfortunately know too little about the AWS APIs. Would you mind taking a look at |
@odrotbohm I added a PR with SQS and SNS integration. I skipped Kinesis as it has been too long since I've used it and we don't have support for it in Spring Cloud AWS anyway. I am happy to answer any questions :) |
Additional event externalization implementations for AWS SNS and SQS. Original pull request: GH-350.
Switch to DelegatingEventExternalizer APIs changed to return CompletableFuture. Imports, formatting. Drop dependencies not needed.
Additional event externalization implementations for AWS SNS and SQS. Original pull request: GH-350.
Switch to DelegatingEventExternalizer APIs changed to return CompletableFuture. Imports, formatting. Drop dependencies not needed.
Additional event externalization implementations for AWS SNS and SQS. Original pull request: GH-350.
Switch to DelegatingEventExternalizer APIs changed to return CompletableFuture. Imports, formatting. Drop dependencies not needed.
Additional event externalization implementations for AWS SNS and SQS. Original pull request: GH-350.
Switch to DelegatingEventExternalizer APIs changed to return CompletableFuture. Imports, formatting. Drop dependencies not needed.
PR merged, thanks for the contribution! |
In addition to Kafka, AMQP and JMS, Modulith could publish externalized events to AWS services: SQS, SNS and perhaps Kinesis.
This can be implemented either here - using AWS SDK directly - or in Spring Cloud AWS where we could use Spring Cloud AWS infrastructure to configure AWS clients.
The text was updated successfully, but these errors were encountered: