Discover how generative AI is transforming the software architect's role from a hands-on coder to a strategic orchestrator. Learn what tasks to stop doing and what new, high-value responsibilities to embrace to stay ahead in an AI-driven world.

Low-code platforms promise incredible speed, but are they solving the right problem? Discover why the real bottleneck to developer productivity isn't coding, and how platform engineering is the key to unlocking true enterprise velocity.

Is migrating from.NET Framework to .NET 8+ worth it? Explore the huge performance gains, security benefits, and cross-platform capabilities. Discover how new AI tools and features make the upgrade more compelling and easier than ever.

Elevate your team's performance with a proven framework for architectural governance. Learn to Codify standards, Automate compliance, and Cultivate a culture of quality to build scalable, maintainable software.

I have been digging into MartenDb and found a sample of the Event Sourcing features included in MartenDb. In this article I walk through this simple Event Sourcing example and describe what is happening.

In today's rapidly evolving business landscape, traditional linear business models are being disrupted by the emergence of platforms. Platform thinking offers a new paradigm for businesses to unlock their potential, create scalable ecosystems, and drive innovation. In this article, we will delve into the world of platform thinking, exploring its benefits and highlighting why businesses should consider adopting this strategic approach.

I recently stumbled upon a Library called FastEndpoints while doing research and it immediately struck me as something I wanted to learn more about. I had started experimenting with Minimal APIs at the time. While I liked that Minimal APIs lower the entry point for simple API creation and are significantly more performant than MVC Controllers, they quickly turn your program.cs file into a jumbled mess with anything beyond trivial. The desire for code organization quickly pushes towards finding a sensible way to orient the code.

Not versioning APIs is one of the biggest issues I see with teams that attempt to implement a distributed architecture. Not supporting multiple versions of an API means all the teams are coupled together and requires downtime to deploy. I've actually seen where this is actually listed as a reason to use a monolith instead of a distributed architecture.

Recently, I became aware of two other options in the .NET Service Bus space that I felt deserved a closer look. Rebus and Brighter. Since Rebus seemed to be similar to NServiceBus and MassTransit I started there.

One of the most painful parts of starting with a new team is to learn all of the nuanced patterns and practices you must adhere to. Often these nuances are not documented and to make matters worse, the common response given for why is, "that is just how we do it here". The tribal knowledge runs so deep it starts to look like cargo cult culture and in some cases it is just that.