Minimal API

You can use the Polly Policy Registry with Minimal APIs and HttpClientFactory. Read on to see how.

I sometimes want to test how an application will handle errors when calling a web service. To do this, I built a simple echo server that responds to any HTTP verb on any URL. Some percentage of the time, the server will return 500 errors. It uses the Simmy package to achieve this.

In the previous post I showed how to pass a Polly Policy Wrap into an Minimal API endpoint with dependency injection. In this post I’ll show to use the Policy Wrap with the Http Client Factory, passing that into the endpoint.

There have been many times that I wanted a simple web API application that takes any request on any url and returns a useful response. Here is how to do just that with both a minimal API endpoint and a full controller.

Polly Policy Wraps let you apply multiple types of resilience to a single operation. Using them with Minimal API Endpoints is easy, read on to see how.

The mediator pattern is very helpful for keeping business logic out of your API endpoints. This post provides a simple example of this with the MediatR library.

All dotnet new... commands take switches that let you tweak the generated project and code. In this example, you will see how to reduce by half the boilerplate code in Program.cs for Web API applications.

Here’s a quick example using IOptions with .NET 6 Minimal API endpoints.

Following on from my previous post on using a memory cache, here I show how to use a distributed memory cache with Redis.

I have used the Microsoft memory cache many times in the past, but didn’t know how to use it with .NET 6 endpoints, so here is a blog post that should save you a little time if you haven’t done it before.