Deprecating Multiple Connections #92
Description
At MX we've run into scaling issues with our RabbitMQ cluster. One of the biggest issues is that our usage of the multiple connections and :concurrency settings features in this library creates a lot of channels. Our production cluster has over 15k channels and consumers registered.
In order to work around these issues we've introduced the new threadpool feature which will take the place of multiple connections and it will allow multiple messages process at the same time for the same consumer. Based on our testing this is within 10% of the throughput of using multiple connections and channels for routes even when processing extremely small messages at high throughputs.
Trying to maintain both of these feature sets is a lot of extra work so we are leaning towards removing support for multiple connections and the :concurrency setting, but if this breaks your usage of the library we would like to know. Please comment below and explain how you are using the library. If you are interested in helping to maintain the features for multiple connections and :concurrency please note that as well.