Use symfony/amazon-sqs-messenger Transport for sending messages

[tomcoonen]

I was wondering if it is an idea now symfony/amazon-sqs-messenger is released, to use the Transport from that package so this package handles only the serverless consumer side?
Does that make sense?

I doesn't seem right to keep that functionality in 2 places?

[mnapoli]

Hi, do you know if there are advantages or downsides for each solution?

[starred-gijs]

I can think of the following possible advantages:

• Possibility to consume via messenger:consume command (sandbox/development) (I have a fork for this now)
• Less maintenance, more in sync with official Symfony package (both use async-aws/sqs client internally now)
• auto-setup feature; if the SQS queue does not exist, it is created on the fly
• Fifo queues support via Stamp (including DeduplicationId)

I compared the TransportInterface:send implementations, but the are very similar, except:

1. All headers encoded in 1 string vs each header in MessageAttribute
2. Support for DeduplicationId
3. Fifo support (not sure)

Possible downside:

• Less control over implementation?

[tomcoonen]

@starred-gijs you beat me to it ;)

I don't have anything to add, point 1, 2 and 3 mentioned by Gijs are most important for my use case.

Once you go serverless, you can use this package to consume the messages.
Would be nice to add some documentation on how to configure this.

[starred-gijs]

Give me a couple of days to create a PR

[tomcoonen]

@starred-gijs if I can help let me know

[starred-gijs]

@tomcoonen Would be helpful if you too could test this!

Im using both the php and symfony serializer in my project, so I need to wait for next release, see #31

ps: be aware that if you use the Symfony Serializer this PR will create a BC issue, because of the different way the MessageAttributes are stored.