Architect Microservices in ASP.NET Core Web API

Author: Dasan | Date: April 11, 2025

1. 🧠 Introduction

Microservices architecture is a modern approach to designing software systems where applications are broken into small, independent services that communicate with each other. With ASP.NET Core, we can easily build scalable, modular, and maintainable microservices.

2. 🔍 Microservices Benefits

• Independent Deployment
• Improved Scalability
• Better Fault Isolation
• Technology Polyglot (use different tech per service)

3. 🧱 Core Components of Microservices in ASP.NET Core

• API Gateway
• Individual Microservices (e.g., Auth, Product, Orders)
• Service Discovery
• Database per service
• Communication (HTTP / gRPC / Messaging)
• Event Bus (e.g., RabbitMQ / Azure Service Bus)

4. 🛠️ Tools & Technologies

• ASP.NET Core Web API
• Ocelot for API Gateway
• Docker & Kubernetes for deployment
• Consul or Steeltoe for Service Discovery
• MassTransit with RabbitMQ for messaging

5. 🧩 Sample Architecture

+------------------+      +-----------------+      +-----------------+
|   API Gateway    | ---> |  Auth Service   | ---> | Auth DB         |
+------------------+      +-----------------+      +-----------------+
        |
        |--> /products       +-----------------+      +-----------------+
        +------------------> | Product Service | ---> | Product DB      |
                             +-----------------+      +-----------------+

        |
        |--> /orders         +-----------------+      +-----------------+
        +------------------> | Order Service   | ---> | Order DB        |
                             +-----------------+      +-----------------+
    

6. 🧪 Sample Service - Product

// ProductService.cs
[ApiController]
[Route("api/[controller]")]
public class ProductController : ControllerBase
{
    [HttpGet]
    public IActionResult GetAll() => Ok(new[] {
        new { Id = 1, Name = "Phone", Price = 699 },
        new { Id = 2, Name = "Laptop", Price = 1200 }
    });
}

7. 🔀 Communication Between Services

You can use:

• HTTP: via HttpClient or Refit
• gRPC: for high-performance communication
• Message Queue: for asynchronous communication

8. 🌐 API Gateway using Ocelot

Ocelot is a lightweight API Gateway that routes requests to appropriate microservices.

{
  "Routes": [
    {
      "DownstreamPathTemplate": "/api/products",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [{ "Host": "localhost", "Port": 7001 }],
      "UpstreamPathTemplate": "/products",
      "UpstreamHttpMethod": [ "GET" ]
    }
  ],
  "GlobalConfiguration": {
    "BaseUrl": "http://localhost:5000"
  }
}

9. 🐳 Dockerizing Microservices

Create a Dockerfile for each microservice:

FROM mcr.microsoft.com/dotnet/aspnet:7.0
WORKDIR /app
COPY . .
ENTRYPOINT ["dotnet", "ProductService.dll"]

10. ⚙️ CI/CD Pipeline

• Use GitHub Actions, Azure DevOps, or GitLab CI
• Each service can be built, tested, and deployed independently

11. 🧠 Best Practices

• Follow Domain-Driven Design
• Use Centralized Logging (e.g., Serilog + Elasticsearch)
• Implement Health Checks for each service
• Handle Retry/Timeout with Polly

12. 📘 Conclusion

Building microservices with ASP.NET Core Web API allows you to scale efficiently, isolate business logic, and deploy faster. Using API Gateway, message queues, and container orchestration will ensure your services are robust, secure, and production-ready.

Next blog: Let’s dive into gRPC Integration in ASP.NET Core Microservices for faster service-to-service communication. ⚡