amqp, SQS, stomp, other messaging/queuing support? about activejob HOT 5 CLOSED

Andrew, it would be great to have more direct support, but when I look at, say, https://github.com/kookster/activemessaging/blob/master/lib/activemessaging/adapters/amqp.rb, there’s too much implementation for what we’d want in the adapters. We need something higher level to wrap around.

But if you want to extract those queue interfaces into separate gems, we could provide adapters for those queue interfaces to ActiveJob. How does that sound?

On May 29, 2014, at 6:14 PM, Andrew Kuklewicz [email protected] wrote:

I've been using and maintaining https://github.com/kookster/activemessaging which also provides an abstraction over different messaging.

If there is interest, I could port over adapters that work directly with amqp, stomp, sqs, and jms queues:

https://github.com/kookster/activemessaging/tree/master/lib/activemessaging/adapters

any interest?

—
Reply to this email directly or view it on GitHub.

from activejob.

👍 on extracting these as separate gems.

from activejob.

Thanks. I see what you mean.

That makes sense for the sending/queueing side of things certainly, though not sure yet what that means for the consumer code, but probably also different gem(s).

I'll pick one and see what I can do (probably SQS or stomp, since I use those most).

from activejob.

@dhh I would also vote up for breaking adapters into separate gems.

from activejob.

I don't see an advantage to having adapters as thin as these in a separate gem, so 👎 on that. But the adapters do need to remain this thin for that to work. So if there's major wrapping work needed, like for amqp, then that does need to come from an external gem.

from activejob.