dotNet6

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.

The release of .NET 7 brings with it a new way to compile and run .NET code - native AOT compilation. This post compares the cold start time of a Lambda function running on .NET 7 after native AOT compilation with the cold start time of a Lambda function running on .NET 6 with the managed runtime. The results are surprisingly good.

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.

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

If you are using IAM auth with Lambda Function URLs, and you want to call the function using HttpClient from a .NET application, you need to sign the request. Read on to see how.

Even though Lambda functions are “serverless”, and even though there is no guarantee how long a function will remain “warm” for, you might still get good use out of a memory cache.

Here are two ways to page through files in an S3 bucket.

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.

When a Lambda function is connected to a VPC, the function can no longer access the internet. One way to resolve this is to use a NAT gateway, read on to see how.