Canary releases sound great until you’re sending 10% of traffic to a new Lambda version and there’s no real traffic at all, meaning you can’t tell whether that 10% is healthy. In this episode, we’ll look at how AWS CodeDeploy solves this with a pre-traffic hook: a separate Lambda function you define that runs logic to invoke your main production Lambda function before any user traffic is shifted. This gives you a way to validate the new version even when your system is quiet, so you’re not guessing whether the deployment is safe.

We Are .NET

When using blue-green deployments with AWS Lambda and CodeDeploy, a silent failure can occur during traffic shifting if there is no real traffic hitting the function at that moment — meaning the health of the new version goes unverified. The solution is to use CodeDeploy's pre-traffic hook, which lets you define a separate Lambda function that proactively invokes your main production Lambda to validate it before traffic is shifted.

The Silent Failure in Blue Green Deployments #serverlessarchitecture #serverless #dotnet #aws