The results of my recent experiment where I evaluated the new Blazor Server Side Rendering (SSR) to see how well it works for migrating from older MVC or Razor Page project incrementally.

I recently converted one of my example projects that used MVC controller based API, Marten Event Sourcing and Rebus to use Wolverine. This article contains some of my initial impressions of Wolverine in that experience and focuses on Wolverine.http API endpoints.

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.

My early exploration and subsequent experiences with building a solution that leverage Marten.

I've been experimenting with Pivotal Cloud Foundry recently and put this quick tutorial together for deploying an ASP.NET Core application using PCF. I was amazed at how easy this was and I'm sure you will be too. This is a quick getting started with Pivotal Cloud Foundry and ASP.NET Core.

I recently had to add a private NuGet package feed to my Azure DevOps build pipeline that creates a Docker container. It looks like a lot of folks are struggling to do the same thing so I put some notes together on how I was able to get it to work without adding secrets to my source control.