Design pattern for multiple messaging systems in a cloud environment

I am working on designing a messaging system in Amazon web services cloud environment. We can use either SQS or any other AMQP systems like RabbitMQ. The decision can be made later, but the design should be robust enough to support any underlying messaging system later.The decision on the underlying system would be taken later based on the pros and cons of each, which is not of a major concern as of now.

Since it should be Producer/Consumer model, I zeroed in on Strategy pattern for the client/producer of messages which will use Spring beans to inject the right strategy implementation based on chosen system. My question is, are there any other pattern which suits this case, may be an Adapter. Why or why not or is Strategy the best pattern for this case?

Thanks for any inputs!!

-Tatha