HTTP API Low volume?

[Christer Tallberg]

In the HTTP API documentation it says that:

"Please note that the HTTP API is not ideal for high performance publishing; the need to create a new TCP connection for each message published can limit message throughput compared to AMQP or other protocols using long-lived connections."

Can someone shade little more light on this? Would it be a problem to use this endpoint for low traffic - for e.g. 50 post requests per day?

Thanks!

[Gabriele Santomaggio]

When you publish a message using HTTP, internally, it creates a new connection/channel for each publishes. So it could be a problem in terms of resources and performance.

In AMQP protocol you have an open connection/channel and send messages through them. So much much faster.

btw 50 messages per day is very low traffic.

-

Gabriele 

[Christer Tallberg]

Alright thanks for your quick reply!

I have though set up some http requests in Postman to produce/consume messages. I experience that sometimes (approx. 2 times per hour) I loose contact with Rabbit and don´t get response. Other times I get response immediately. Is this normal behavior as it´s meant for management?