Scalability with EasyNetQ?

I checked that issue answer:

Does EasyNetQ use a new thread to deal with Subscribe message?` Is using one single thread to consume and one single thread to publish.

It’s not clear to me whether EasyNetQ is actually creating a new thread per subscribe and create a new one per publish, or are they threadpool threads?

How this can be customized or controlled?

We are thinking using an actor framework to process the messages more horizontally.

[Pliner]

Hi @ehouarn-perret,

Now there is one publish channel per bus(and we invoke commands to it in single thread). I hope we will introduce pools of publish channels after 4.0.

Merely the same situation with consumer side(multiple channels and single thread) and as I understand there is no limitation to have multithreaded consumer dispatcher, but instead it’s better to offload the handlers to thread pool by Task.Run.

[sungam3r]

See this

You can use your own IConsumerDispatcher / IConsumerDispatcherFactory and configure it via DI:

IServiceRegister.Register<IConsumerDispatcherFactory, MyConsumerDispatcherFactory>();

Factory:

internal sealed class MyConsumerDispatcherFactory : IConsumerDispatcherFactory
    {
        private readonly Lazy<IConsumerDispatcher> dispatcher;

        public MyConsumerDispatcherFactory(ConnectionConfiguration configuration)
        {
            if (configuration == null)
                throw new ArgumentNullException(nameof(configuration));

            dispatcher = new Lazy<IConsumerDispatcher>(() => new MyConsumerDispatcher(configuration));
        }

        public IConsumerDispatcher GetConsumerDispatcher() => dispatcher.Value;

        public void OnDisconnected()
        {
            if (dispatcher.IsValueCreated)
                dispatcher.Value.OnDisconnected();
        }

        public void Dispose()
        {
            if (dispatcher.IsValueCreated)
                dispatcher.Value.Dispose();
        }
    }