Is there a way to resolve a new scope per message?

[justinpenguin45]

This would be analogous to asp.net core's scope per request lifetime?

[kmcclellan]

You can. The consumer itself is a singleton, but it's a good idea to create a scope for each message using IServiceScopeFactory. Typically, users of this library will implement BackgroundService and inject IConsumer<TKey, TValue> via the constructor. Your classes might look something like this:

public class ConsumerService(IConsumer<byte[], byte[]> consumer, IServiceScopeFactory scopes) : BackgroundService
{
    protected override async Task ExecuteAsync(CancellationToken stoppingToken)
    {
        consumer.Subscribe("topic1");

        while (true)
        {
            var result = consumer.Consume(stoppingToken);

            using var scope = scopes.CreateScope();
            var processor = scope.ServiceProvider.GetRequiredService<ConsumerProcessor>();

            await processor.ProcessResult(result);
        }
    }
}

// Registered as scoped so you can inject other transient/scoped dependencies.
public class ConsumerProcessor
{
    public Task ProcessResult(ConsumeResult<byte[], byte[]> result)
    {
        return Task.Delay(100);
    }
}

This is similar to the example in the DI documentation.

I hope to add an implementation of IHostedService to this library soon that takes care of this boilerplate and also lets you configure multi-threading and at least once processing.

[justinpenguin45]

Great! Yes that would be awesome if you added that. Thanks for the quick reply!