Still active project?

[jnormen]

Hi as all know the .net community open source world is little messy now as for other parts of the world.

We used Masstransit for Kafka and I'm looking for a solid project to replace it with.
I do not want to build my own, have no time for that

So I wonder how's the plan here? with this project? will it update continuously? be alive? or end up in the same situation as Mass transit etc?

I investigating:
Wolverine but there are some limits and I have no time to contribute to changes :(
Brighter but also some limitations I do not like

your project looks promising in what i want to do:

• Have the possibility to use different api-keys for each producer

• Have the possibility to use different api-keys for each consumer and offsets etc..

• Add middleware's for Fluent validation

• Add middleware for extra open telemetry logging and metrics

• Add custom error handling and global error handlings

• opt in auto commit or not

• add my own fallback handler for messages I want to skip because of errors etc, not send them to a queue but in for example blog storage

I think your lib can do all this when I read the documentation, but I'm worried about the contributions etc.

I'm a consultant so I will not use it for my own projects therefore its kind of import

I loved the way you abstracted confluence Kafka :)

[BEagle1984]

Thanks for reaching out!

You're absolutely right, there's been a lot of uncertainty in the .NET OSS space lately.

Silverback is very much alive and actively maintained. The latest bug fix was shipped just a few weeks ago, and a major v5.0.0 overhaul is on the way, bringing several long-awaited features.

While it started as a side project of mine, Silverback is now a key part of the core business systems at Swiss Post and runs in production under real-world, high-stakes conditions. It has grown far beyond a personal experiment and isn’t going anywhere anytime soon.

Regarding licensing and long-term outlook, I have no plans to make Silverback commercial. As long as I’m behind it, it will remain open-source and free. I’m not a fan of how some other libraries have handled this recently, and I don’t intend to follow that route.

Of course, I can’t guarantee what will happen decades from now, but today the project is solid, active, and moving forward with a clear focus.

Really glad to hear that Silverback's design and feature set align with what you're looking for.