.NET Microservices with Docker and Kubernetes

Microservices architecture is a game-changer for building scalable, maintainable, and high-performing applications. When combined with Docker and Kubernetes, .NET microservices gain efficiency, portability, and resilience. This article explores how to build, containerize, and orchestrate .NET microservices using Docker and Kubernetes, with a step-by-step guide and practical commands.

Why Use Microservices with Docker and Kubernetes?

• Scalability: Easily scale individual services based on demand.
• Resilience: If one microservice fails, the entire system doesn’t crash.
• Flexibility: Services can be written in different technologies and deployed independently.
• Portability: Docker containers ensure consistency across development, testing, and production.

Prerequisites

Before starting, ensure you have the following installed:

• .NET SDK
• Docker
• Kubernetes (Minikube or a managed service like AKS)
• kubectl (Kubernetes CLI)
• Helm (Optional, for managing Kubernetes applications)

Step 1: Create a .NET Microservice

Run the following command to create a new .NET Web API project:

mkdir DotNetMicroservice && cd DotNetMicroservice
dotnet new webapi -n ProductService
cd ProductService
dotnet restore

Modify Program.cs to use minimal APIs:

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

app.MapGet("/products", () => new[] { new { Id = 1, Name = "Laptop" } });

app.Run();

Test the API:

dotnet run

Step 2: Create a Dockerfile

Create a Dockerfile in the ProductService directory:

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
WORKDIR /app
EXPOSE 80

FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /src
COPY . .
RUN dotnet restore
RUN dotnet publish -c Release -o /app

FROM base AS final
WORKDIR /app
COPY --from=build /app .
ENTRYPOINT ["dotnet", "ProductService.dll"]

Step 3: Build and Run Docker Container

docker build -t product-service .
docker run -d -p 5000:80 --name product-service-container product-service

Verify that the container is running:

docker ps

Access the API:

curl http://localhost:5000/products

Step 4: Deploy to Kubernetes

Create Kubernetes Deployment YAML

Create deployment.yaml:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: product-service
spec:
  replicas: 2
  selector:
    matchLabels:
      app: product-service
  template:
    metadata:
      labels:
        app: product-service
    spec:
      containers:
      - name: product-service
        image: product-service:latest
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: product-service
spec:
  selector:
    app: product-service
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80
  type: LoadBalancer

Apply the deployment:

kubectl apply -f deployment.yaml

Verify the deployment:

kubectl get pods

Step 5: Scale and Manage Microservices

Scale the service:

kubectl scale deployment product-service --replicas=5

Check logs:

kubectl logs -l app=product-service

Step 6: Monitor and Manage with Helm (Optional)

helm install product-service ./helm-chart
kubectl get services

Conclusion

Using .NET with Docker and Kubernetes simplifies the deployment and management of microservices. By containerizing .NET applications and orchestrating them with Kubernetes, developers can build scalable, resilient, and efficient distributed systems.

FAQ

1. What is the advantage of using Kubernetes with .NET?

Kubernetes helps manage, scale, and deploy .NET microservices efficiently.

2. Can I use Docker Compose instead of Kubernetes?

Yes, but Kubernetes is better suited for production-grade scalability.

3. How do I secure a .NET microservice in Kubernetes?

Use TLS, authentication, and network policies to enhance security.

4. What cloud services support Kubernetes for .NET apps?

Azure Kubernetes Service (AKS), Amazon EKS, and Google Kubernetes Engine (GKE).

5. How do I monitor .NET microservices in Kubernetes?

Use tools like Prometheus, Grafana, and Azure Monitor.

Let us know your thoughts in the comments below! 🚀