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 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.

Goldratt provides 6 thinking processes as part of TOC and two of them are systematic approaches for resolving conflict. These thinking processes are Evaporating Cloud (Conflict Resolution Diagram) and Current Reality Tree (CRT). The evaporating cloud process is the simpler approach that can be used to solve most conflicts and is a frequently used tool in my toolbelt.

The Theory of Constraints (TOC) is a management philosophy and methodology developed by Eliyahu M. Goldratt. It focuses on improving organizational performance by identifying and addressing constraints, which are bottlenecks or limiting factors that impede the system's ability to achieve its goals.

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.

If you have not run across Steeltoe, it is a set of libraries that address most of the cross cutting concerns you deal with when building microservices. Logging, Configuration, Health Checks, Traces, Service Discovery, etc.