threedotslabs/watermill-amazonsqs

watermill-amazonsqs's Issues

Help needed?

Hey @m110 ,
I have been enjoying your content and your course (so far 😉 )! At work, we are on the journey to an event-driven-architecture and are leveraging SQS in specific quite a bit. We would really like to test out watermill as the backbone for this architecture but this package seems a bit "underdeveloped" (no offense!). Do you have concrete plans to maintain and support it or is this more something the community should take care of? I am just curious if you are looking for help to maintain/develop this package to bring it to a stable release? Or do you suggest to better fork and maintain in private?

Greetings from Berlin!

Refactor the utils.go and marshaller/unmarshaller into separate packages

Move those common components out of the amazonsqs package into a separate utils package?

Use aws-sdk-go-v2

The aws-sdk-go-v2 library has been available for quite a while and is pretty mature. Maybe it's a good idea to upgrade from aws-sdk-go: https://github.com/aws/aws-sdk-go-v2

proposal(sqs): automatic encoding of messages

Goal

Ensure payloads send using the publisher confirm as valid message types. Users of watermill should not be concerned with ensuring that their payload is valid for the publisher they're using (Apart from potential sizing issues).

See https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SendMessage.html detailing the supported characters for a payload

Changes

Check the message being published for any invalid characters, if it is found, base64 the message and add a metadata item with key _watermill_encoding & value base64.

The subscriber is auto updated to check for the _watermill_encoding metadata value, reversing the base64 encoding if it is found.