Sponsor: Using RabbitMQ or Azure Service Bus in your .NET systems? Well, you could just use their SDKs and roll your own serialization, routing, outbox, retries, and telemetry. I mean, seriously, how hard could it be?
In 2007 there was a movement in the .NET community dubbed “ALT.NET”. A community was formed by individuals who believed there to be a “better” way from the tooling, frameworks, practices and principles provided by Microsoft. The initial release of Linq to Entities (Entity Framework) was really a starting point for discussion since it did not support POCO’s and was not persistence ignorant. ALT.NET was about challenging the status quo. Although some might not be familiar with with the ALT.NET movement, you can thank it for helping the common practice of: Inversion of Control (Dependency Injection), Persistence Ignorant ORM’s, and SOLID principles. So what happened to the community? Was it a failure since it is no longer as active? Or was it a success because many of the alternatives are now the “norm”? I believe it to be both. We need to continue challenging the status quo. Individually and as a community. Innovation and process improvement can only come from alternative thinking. Have pride for the software you develop (Manifesto for Software Craftsmanship) and improve upon the existing practices.