Microservices in C#: Architecture and Practice from A to Z

Introduction to Microservices in C#

Microservice architecture has become the de facto standard for building complex, scalable, and fault-tolerant applications. Unlike a monolith, where all code is combined into a single process, microservices break the system into small, independently deployable services. The .NET platform (C#) provides all the necessary tools for creating professional microservices: from ASP.NET Core for web APIs to libraries for working with queues, containerization, and orchestration.

In this article, we will cover the full path from designing the architecture to the practical implementation of a microservice in C# with code examples.

1. Fundamentals of Microservice Architecture

Principles and Anti-Patterns

Before writing code, it is important to understand the key principles:

\n
• Single Responsibility (SRP): Each service is responsible for one business function (e.g., order service, payment service).
\n
• Loose Coupling: Services communicate over the network (HTTP, gRPC, queues) and do not know about each other's internal structure.
\n
• Independent Deployment: You can update one service without stopping others.
\n
• Data Decentralization: Each service owns its own database (Database per Service).
\n

Anti-patterns to avoid: overly small services (nanoservices), shared database, synchronous call chains (chattiness).

Communication Between Services

For microservice interaction in C#, the following are used:

\n
• Synchronous: REST API (HTTP/JSON) or gRPC (binary protocol, faster).
\n
• Asynchronous: Message queues (RabbitMQ, Azure Service Bus, Kafka) — the preferred method for loose coupling.
\n

2. Practical Implementation of a Microservice in C#

Example: Order Management Service

Let's create a simple microservice using ASP.NET Core 8. We'll use Clean Architecture to separate layers.

Step 1: Project and Structure

dotnet new webapi -n OrderService\ncd OrderService

Create folders: Controllers, Models, Services, Data.

Step 2: Data Model

// Models/Order.cs\npublic class Order\n{\n    public int Id { get; set; }\n    public string CustomerName { get; set; }\n    public decimal TotalAmount { get; set; }\n    public DateTime CreatedAt { get; set; }\n}

Step 3: Database Context (Entity Framework Core)

// Data/OrderDbContext.cs\npublic class OrderDbContext : DbContext\n{\n    public OrderDbContext(DbContextOptions<OrderDbContext> options) : base(options) { }\n    public DbSet<Order> Orders { get; set; }\n}

Step 4: Service Layer

// Services/IOrderService.cs\npublic interface IOrderService\n{\n    Task<Order> CreateOrderAsync(Order order);\n    Task<List<Order>> GetAllOrdersAsync();\n}\n\n// Services/OrderService.cs\npublic class OrderService : IOrderService\n{\n    private readonly OrderDbContext _context;\n    public OrderService(OrderDbContext context)\n    {\n        _context = context;\n    }\n\n    public async Task<Order> CreateOrderAsync(Order order)\n    {\n        _context.Orders.Add(order);\n        await _context.SaveChangesAsync();\n        return order;\n    }\n\n    public async Task<List<Order>> GetAllOrdersAsync()\n    {\n        return await _context.Orders.ToListAsync();\n    }\n}

Step 5: Controller

// Controllers/OrdersController.cs\n[ApiController]\n[Route("api/[controller]")]\npublic class OrdersController : ControllerBase\n{\n    private readonly IOrderService _orderService;\n    public OrdersController(IOrderService orderService)\n    {\n        _orderService = orderService;\n    }\n\