Event Sourcing Pattern — Audit & Replay Systems

Introduction

Event Sourcing Pattern — Audit & Replay Systems is essential for .NET architects building ShopNest Enterprise Architecture Platform — Toolliyo's 69-article design patterns master path covering GoF creational, structural, and behavioral patterns; enterprise patterns (Repository, CQRS, Saga, Outbox); microservices; ASP.NET Core architecture; and senior interview prep. Every article includes minimum two mandatory real-world examples.

In Indian delivery projects (TCS, Infosys, Wipro), interviewers expect event sourcing with real banking, e-commerce, or SaaS examples — not toy animal demos. This article delivers production depth on Payments.

After this article you will

• Explain Event Sourcing in plain English and in enterprise architecture terms
• Implement Event Sourcing in ShopNest Enterprise Architecture (Payments)
• Compare anti-pattern vs production-ready pattern implementation
• Answer fresher and senior design pattern interview questions confidently
• Connect this lesson to Article 43 and the 69-article Design Patterns roadmap

Prerequisites

• Software: .NET 10 SDK, VS 2022 or VS Code, xUnit + Moq
• Knowledge: C# basics, SOLID principles
• Previous: Article 41 — Circuit Breaker Pattern — Cloud-Native Fault Tolerance
• Time: 24 min reading + 30–45 min hands-on

Concept deep-dive

Level 1 — Analogy

Event Sourcing on ShopNest Enterprise Architecture is a proven blueprint for the Event Sourcing problem in growing platforms.

Level 2 — Technical

Event Sourcing structures enterprise ShopNest Payments — persistence abstraction, command/query split, reliable messaging, and resilience with Polly.

Level 3 — Architecture placement

[Client / API Gateway]
       ▼
[Application Layer — Handlers, Strategies, Commands]
       ▼
[Domain Layer — Entities, Domain Events, Specifications]
       ▼
[Infrastructure — EF Core, Message Bus, Polly, Cache]
       ▼
[Pattern Registration — Program.cs DI lifetimes]
       ▼
[xUnit + Moq — pattern behavior isolated]

Project structure

ShopNest.EnterpriseArchitecture/
├── ShopNest.Domain/           ← Entities, domain events, interfaces
├── ShopNest.Application/      ← Commands, queries, handlers (MediatR)
├── ShopNest.Infrastructure/   ← EF Core, Redis, RabbitMQ, Polly
├── ShopNest.Api/              ← ASP.NET Core Web API + Minimal APIs
├── ShopNest.Workers/          ← Hosted services, outbox processors
└── ShopNest.Gateway/          ← YARP API Gateway

Hands-on implementation — Payments

Implement Event Sourcing in C# for Payments: write a class or method, compile, and verify with a console or unit test.

1. Open a console or class library project.
2. Implement the concept in a focused class or method.
3. Add null checks and meaningful exception messages.
4. Run dotnet build and dotnet test.
5. Review naming and SOLID boundaries.

Anti-pattern (god class, swallowed exceptions, magic strings)

// ❌ BAD — no pattern, tight coupling, untestable
public class OrderController : ControllerBase {
    public IActionResult Place(OrderDto dto) {
        var conn = new SqlConnection("Server=.;...");
        // direct SQL, no repository, no UoW, no error handling
        return Ok();
    }
}

Production-style C# code

// ✅ CORRECT — Event Sourcing on ShopNest (Payments)
public sealed class PlaceOrderHandler(
    IOrderRepository repo,
    IUnitOfWork uow,
    IPublisher events) : IRequestHandler<PlaceOrderCommand, Result<int>>
{
    public async Task<Result<int>> Handle(PlaceOrderCommand cmd, CancellationToken ct) {
        var order = Order.Create(cmd.CustomerId, cmd.Lines);
        await repo.AddAsync(order, ct);
        await events.Publish(new OrderPlacedEvent(order.Id), ct);
        await uow.SaveChangesAsync(ct);
        return Result.Success(order.Id);
    }
}

Complete example

public interface IEventSourcingService { Task ExecuteAsync(CancellationToken ct); }
public sealed class EventSourcingService : IEventSourcingService { /* ShopNest Payments */ }

Real-World Example 1 — Retail POS System

MANDATORY: Enterprise-grade Event Sourcing Pattern implementation in a production retail pos system.

Business requirement

Point-of-sale terminals need offline resilience and sync when connectivity returns — product catalog and pricing must stay consistent.

Why Event Sourcing Pattern is needed

Without Event Sourcing Pattern, the Retail POS System team at ShopNest faces tight coupling, untestable code, and painful refactors every sprint. Event Sourcing Pattern decouples responsibilities so the Payments module can evolve independently while meeting scalability and compliance requirements.

Architecture

[Client/API] → [Event Sourcing Pattern Abstraction]
  → [ShopNest.Payments Service] → [EF Core / Redis / Message Bus]
  → [Downstream: Audit, Notifications, Reporting]

Tech stack: Repository + Unit of Work, local SQLite cache, sync hosted service

Full working code

// REAL-WORLD EXAMPLE 1: Retail POS System
// ShopNest Enterprise Architecture — Payments module
// Pattern: Event Sourcing

namespace ShopNest.Architecture.Payments;

public interface IEventSourcingService
{
    Task ExecuteAsync(EventSourcingRequest request, CancellationToken ct = default);
}

public sealed class RetailPOSSystemEventSourcingService : IEventSourcingService
{
    private readonly ILogger _logger;

    public RetailPOSSystemEventSourcingService(ILogger logger)
        => _logger = logger;

    public async Task ExecuteAsync(EventSourcingRequest request, CancellationToken ct)
    {
        _logger.LogInformation("[Event Sourcing] Processing {Domain} request {Id}",
            "Retail POS System", request.Id);

        // Production implementation — see Program.cs for DI registration
        await Task.Delay(10, ct);
        return Result.Success(request.Id);
    }
}

// Register in Program.cs:
// builder.Services.AddScoped();

Benefits achieved

• Loose coupling — swap implementations without changing controllers
• Unit testable — mock IEventService in xUnit tests
• Scalable — horizontal scaling of Payments workers under load
• Maintainable — new business rules added via new classes, not if-else chains

Real-World Example 2 — Insurance Claims Processing

MANDATORY: Second complete example in a different domain — Insurance Claims Processing.

Business problem

Claims pass through validation, adjuster review, approval chains, and payout — each step has different business rules.

Why Event Sourcing Pattern solves it

In Insurance Claims Processing, Indian IT delivery teams (TCS, Infosys, Wipro lateral rounds) frequently ask how Event Sourcing Pattern applies to distributed systems. This example shows production-level implementation with ASP.NET Core integration, not toy animal/car demos.

Production implementation

// REAL-WORLD EXAMPLE 2: Insurance Claims Processing
// ShopNest Enterprise Architecture — Payments module
// Pattern: Event Sourcing

namespace ShopNest.Architecture.Payments;

public interface IEventSourcingService
{
    Task ExecuteAsync(EventSourcingRequest request, CancellationToken ct = default);
}

public sealed class InsuranceClaimsProcessingEventSourcingService : IEventSourcingService
{
    private readonly ILogger _logger;

    public InsuranceClaimsProcessingEventSourcingService(ILogger logger)
        => _logger = logger;

    public async Task ExecuteAsync(EventSourcingRequest request, CancellationToken ct)
    {
        _logger.LogInformation("[Event Sourcing] Processing {Domain} request {Id}",
            "Insurance Claims Processing", request.Id);

        // Production implementation — see Program.cs for DI registration
        await Task.Delay(10, ct);
        return Result.Success(request.Id);
    }
}

// Register in Program.cs:
// builder.Services.AddScoped();

Scalability benefits

• Supports multi-region deployment on Azure with independent scaling
• Integrates with ShopNest distributed events (RabbitMQ) for async workflows
• Redis caching reduces database load for read-heavy Insurance operations
• Polly resilience policies handle transient failures in cloud-native environments

Pattern variations & ASP.NET Core integration

Modern C# 14 uses primary constructors, records, and DI. Register Event Sourcing abstractions in Program.cs with appropriate lifetimes — Singleton for stateless, Scoped for request-bound, Transient for lightweight factories.

Microservices: Apply Event Sourcing within bounded contexts — each ShopNest service (Payments) owns its implementation.

Pattern comparison & when NOT to use

Compare Event Sourcing with similar patterns. Avoid overengineering — if a simple function or DI registration suffices, do not force a pattern. Senior architects value judgment over pattern count.

Unit testing the pattern

public class EventSourcingPatternTests
{
    [Fact]
    public async Task ExecuteAsync_ReturnsSuccess()
    {
        var mock = new Mock<IEventSourcingService>();
        mock.Setup(s => s.ExecuteAsync(default)).ReturnsAsync(Result.Success());
        var result = await mock.Object.ExecuteAsync(default);
        Assert.True(result.IsSuccess);
    }
}

Pattern recognition

Object creation pain → Creational. Composing subsystems → Structural. Algorithm/communication variation → Behavioral. Persistence/messaging → Enterprise. Multi-service → Cloud patterns. ASP.NET pipeline → Middleware/Options/Hosted Service.

Common errors & fixes

• Singleton with mutable state shared across requests — Use Singleton only for stateless services; keep request state Scoped.
• Factory explosion — new class per trivial variation — Use Strategy or simple DI when behavior differs slightly, not Abstract Factory.
• Repository wrapping every EF call without domain logic — Repository adds value for testability and query composition — not as a pass-through.
• Saga/CQRS on a CRUD app with 3 tables — Start with simple layered architecture; add patterns when complexity demands.

Best practices

• 🟢 Name patterns by problem solved, not GoF catalog page number
• 🟢 Register abstractions in DI — depend on interfaces, not concretions
• 🟡 Match DI lifetime to pattern (Singleton vs Scoped)
• 🟡 Write one xUnit test proving the pattern's core behavior
• 🔴 Do not apply Saga/CQRS/Event Sourcing on simple CRUD
• 🔴 Document when you chose NOT to use a pattern — interviews love this

Interview questions

Fresher level

Q1: What is the Event Sourcing pattern and when would you use it?
A: Event Sourcing solves a specific recurring problem on ShopNest Payments. Explain intent, structure (participants), and one real example — then state when NOT to use it.

Q2: Event Sourcing vs similar patterns — how do you choose?
A: Compare intent and consequences; e.g. Strategy vs State, Repository vs DAO, Mediator vs Observer — pick by change axis.

Q3: How do design patterns relate to SOLID?
A: Patterns implement SOLID — Strategy/OCP, Repository/DIP, SRP via focused classes. SOLID is why; patterns are how.

Mid / senior level

Q4: Repository pattern — benefits and pitfalls?
A: Benefits: testability, query composition. Pitfalls: leaky abstraction, generic repo anti-pattern, duplicating EF features.

Q5: When would you NOT use a design pattern?
A: Simple CRUD, prototypes, or single-developer utilities — YAGNI until complexity appears.

Q6: How are patterns asked in TCS/Infosys lateral interviews?
A: Scenario-based: "Design payment retry" → Retry + Circuit Breaker; "Split monolith" → Strangler + API Gateway.

Coding round

Implement Event Sourcing for ShopNest Payments: interface, concrete class, DI registration, and xUnit test with Moq.

builder.Services.AddScoped<IEventSourcingService, EventSourcingService>();

public sealed class EventSourcingService : IEventSourcingService
{
    public Task<Result> ExecuteAsync(CancellationToken ct) => Task.FromResult(Result.Success());
}

Summary & next steps

• Article 42: Event Sourcing Pattern — Audit & Replay Systems
• Module: Module 5: Modern Enterprise Patterns · Level: INTERMEDIATE · Type: ENTERPRISE
• Applied to ShopNest Enterprise Architecture — Payments

Previous: Circuit Breaker Pattern — Cloud-Native Fault Tolerance
Next: Domain Events Pattern — Complete Guide

Practice: Apply today's pattern in one module — commit with feat(patterns): article-42.

FAQ