Olawale Lawal
Writingtransmissions

#Microservice

Running several .NET services together: API gateways, reverse proxies, shared secrets, correlated logs and the failure modes of distributed calls.

5 posts

2025

  1. CI/CD for .NET on GitHub Actions: Change Detection, Docker Caching and Deploys

    A production GitHub Actions pipeline for a multi-service .NET solution: build only what changed, cache NuGet and Docker layers, publish to GHCR, deploy over SSH with Compose, and the failure modes that cost the most time.

  2. Centralized Secrets for .NET Services with HashiCorp Vault

    Run Vault in Docker, lock each .NET service down with AppRole and policies, layer KV secrets over appsettings.json with VaultSharp, issue short-lived database credentials, and fix the 403s and sealed-vault errors you will meet.

2024

  1. Using Caddy as a Reverse Proxy with SSL Termination and Cloudflare in Docker Compose

    Set up Caddy as a reverse proxy with automatic HTTPS using Let's Encrypt SSL and Cloudflare DNS validation in Docker Compose.

  2. Using Ocelot as an API Gateway in a .NET Core Microservices Architecture

    Centralize routing, authentication and load balancing in .NET Core microservices with Ocelot API Gateway.

2023

  1. Structured Logging in .NET with Serilog and Seq

    Set up Serilog and Seq in ASP.NET Core properly: bootstrap logging, request logging, trace correlation across services, destructuring, Seq queries, alerts, and the reasons your events never show up.