You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our application has an API that contains the necessary code for connecting to and publishing messages on RabbitMQ. Though the connection and message publishing takes only around 600-700 microseconds, the execution time for other functionalities is merely 400-500 microseconds. However, despite this, the process mentioned above affects the API response time by approximately 1-1.5 seconds, which is unacceptable. To resolve this problem, I have set up an app singleton for RabbitMQ.
How can I make the RabbitMQ connection session keep live as a background process like Background Worker, and share publish a message from multiple HTTP requests to the background process to publish this message in the RabbitMQ queue?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Our application has an API that contains the necessary code for connecting to and publishing messages on RabbitMQ. Though the connection and message publishing takes only around 600-700 microseconds, the execution time for other functionalities is merely 400-500 microseconds. However, despite this, the process mentioned above affects the API response time by approximately 1-1.5 seconds, which is unacceptable. To resolve this problem, I have set up an app singleton for RabbitMQ.
How can I make the RabbitMQ connection session keep live as a background process like Background Worker, and share publish a message from multiple HTTP requests to the background process to publish this message in the RabbitMQ queue?
Beta Was this translation helpful? Give feedback.
All reactions