How to use solace as message broker with celery for quart application

General Discussions
1

Hii

We have tried to implement to integrate solace and celery using kombu transport but as celery amqp is .9 and solace 1.0 it is not working. Is there anyway to make celery work on amqp or any other protocol

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Looking at the documentation, I can explain why integrating Celery with PubSub+ event broker using Kombu transport presents a compatibility challenge:

  1. Protocol Version Mismatch:
  • PubSub+ event broker only supports AMQP 1.0
  • Celery/Kombu uses AMQP 0.9.1
  • These versions are incompatible with each other
  1. No Direct Integration:
  • There is no direct connector or adapter provided by Solace for Celery/Kombu integration
  • The protocol version difference means standard AMQP connectivity won’t work

Given these limitations, you would need to consider alternative approaches:

  1. Use a different message broker that supports AMQP 0.9.1 for Celery
  2. Implement a custom bridge/adapter between Celery and PubSub+ event broker
  3. Consider using a different integration mechanism supported by both systems

Relevant sources:

3

Hi @Ashok1993,

I think you have two options:

  1. It looks like celery kombu supports qpid as a transport type, that should be AMQP v1. Will that work for you?
  2. If you don’t already have a large investment of code could you consider just using a different messaging API, such as using Solace’s Python API directly. Or are you looking to move a bunch of existing apps already using celery?

Hope that helps!