Repository Refactoring — Complete Guide

Introduction

Repository Refactoring — Complete Guide is essential for .NET developers building ShopNest Enterprise Clean Architecture Platform — Toolliyo's 100-article SOLID master path covering SRP, OCP, LSP, ISP, DIP, refactoring, Clean Architecture, and ten enterprise projects. Every article includes minimum two detailed real-world examples with bad code before good code.

In Indian delivery projects (TCS, Infosys, Wipro), interviewers expect repository refactoring with HDFC banking SRP fixes, Flipkart OCP payment strategies, and legacy refactoring stories — not toy animal demos. This article delivers production depth on Authentication.

After this article you will

• Explain Repository Refactoring in plain English and in SOLID / maintainable OOP terms
• Apply repository refactoring to ShopNest Clean Architecture (Authentication module)
• Compare bad architecture vs production-ready SOLID refactor
• Answer fresher and senior SOLID / clean architecture interview questions confidently
• Connect this lesson to Article 79 and the 100-article SOLID roadmap

Prerequisites

• Software: .NET 10 SDK, VS 2022 or VS Code, xUnit + Moq NuGet packages
• Knowledge: C# basics
• Previous: Article 77 — Controller Refactoring — Complete Guide
• Time: 28 min reading + 30–45 min hands-on refactor

Concept deep-dive

Level 1 — Analogy

Refactoring with SOLID is renovating floor-by-floor while the shop stays open — characterization tests are your safety net.

Level 2 — Technical

Repository Refactoring refactors legacy ShopNest code — extract interfaces, introduce DI, shrink controllers, and add characterization tests before changes.

Level 3 — Clean Architecture view

[API Controller / Worker]
       ▼
[Application Layer — Handlers / Services]
       ▼  depends on abstractions
[Domain Layer — Entities / Value Objects]
       ▼  implemented by
[Infrastructure — EF Core, Email, Payment Gateways]
       ▼
[DI Container — Program.cs registrations]
       ▼
[xUnit + Moq — isolated unit tests per principle]

Project structure

ShopNest.CleanArchitecture/
├── ShopNest.Domain/           ← Entities, value objects (no dependencies)
├── ShopNest.Application/      ← Handlers, interfaces, DTOs
├── ShopNest.Infrastructure/   ← EF Core, email, payment gateways
├── ShopNest.Api/              ← Controllers, Program.cs DI
└── ShopNest.Tests/            ← xUnit + Moq per module (Authentication)

Hands-on implementation — Authentication

Apply Repository Refactoring in ShopNest Clean Architecture for Authentication: identify violation, extract interface, refactor with DI, and verify with xUnit + Moq.

1. Open the ShopNest module (Orders, Payments, etc.) and locate the god class or violation.
2. Extract a focused interface with one responsibility (SRP) or strategy (OCP).
3. Register implementations in Program.cs with constructor DI.
4. Write xUnit tests with Moq for the new abstraction.
5. Run dotnet test and compare cyclomatic complexity before/after refactor.

Anti-pattern (god class, if/else chains, concrete new())

// ❌ BAD — god class violates SRP, tight coupling, untestable
public class OrderService {
    public void PlaceOrder(Order o) {
        Validate(o);
        _context.Orders.Add(o);
        _context.SaveChanges();
        SendEmail(o.CustomerEmail);
        GenerateInvoicePdf(o);
    }
}

Production-style SOLID refactor

// ✅ CORRECT — Repository Refactoring on ShopNest (Authentication) — SOLID applied
public sealed class PlaceOrderHandler(
    IOrderRepository repo,
    INotificationService notify) : IRequestHandler<PlaceOrderCommand, Result>
{
    public async Task<Result> Handle(PlaceOrderCommand cmd, CancellationToken ct) {
        var order = Order.Create(cmd.CustomerId, cmd.Items);
        await repo.AddAsync(order, ct);
        await notify.OrderPlacedAsync(order, ct);
        return Result.Success(order.Id);
    }
}

Complete example

// Repository Refactoring — ShopNest.Authentication module
// Step 1: characterization tests
// Step 2: extract interface
// Step 3: DI registration

The problem before SOLID

Without SOLID, ShopNest teams hit: tight coupling, god classes, untestable controllers, merge conflicts, and fear of refactoring. Indian IT projects (TCS, Infosys, Wipro) lose sprints when legacy code has no clear boundaries.

• Tight coupling — change SMS provider, break ledger posting
• Testing difficulty — cannot mock database from controller
• Scalability — monolith teams block each other
• Bug-prone — one class, five reasons to change

Real-time refactoring walkthrough — SOLID

Step 1: Identify violation → Step 2: Extract interface → Step 3: Split responsibilities → Step 4: Register in DI → Step 5: Add unit tests. Commit each step separately for safe code review.

Real-World Example 1 — Apollo Hospital — Legacy Refactoring to SOLID

MANDATORY enterprise scenario (Healthcare): Repository Refactoring applied in ShopNest Clean Architecture Authentication.

Business problem

Monolithic PatientModule mixed UI, DB, and billing. Strangler fig + SOLID: extract IPatientRepository, IBillingService; MVC controller thin; MediatR handlers per use case.

Before SOLID — bad design

public class PatientPage {
    public void Load(int id) {
        var conn = new SqlConnection("...");
        // 200 lines SQL + HTML generation + billing calc
    }
}

After SOLID — production design

public class GetPatientQueryHandler(IPatientRepository repo, IBillingService billing)
    : IRequestHandler<GetPatientQuery, PatientDashboardVm> {
    public async Task<PatientDashboardVm> Handle(GetPatientQuery q, CancellationToken ct) {
        var patient = await repo.GetAsync(q.PatientId, ct);
        var balance = await billing.GetBalanceAsync(q.PatientId, ct);
        return PatientDashboardVm.From(patient, balance);
    }
}

Outcome

Team of 6 parallelized on Patient, Billing, Labs modules — merge conflicts dropped 70%.

Real-World Example 2 — HDFC Core Banking — Transfer Service SRP Violation Fix

MANDATORY enterprise scenario (Indian Banking): Repository Refactoring applied in ShopNest Clean Architecture Authentication.

Business problem

A 2,400-line TransferService handled validation, ledger posting, SMS, fraud checks, and PDF receipts. One change to SMS template broke fund transfers in production. SRP split into ITransferValidator, ILedgerService, IFraudChecker, INotificationService.

Before SOLID — bad design

// ❌ GOD CLASS — violates SRP
public class TransferService {
    public void Transfer(Account from, Account to, decimal amount) {
        ValidateAccounts(from, to);
        CheckFraud(from, amount);
        UpdateLedger(from, to, amount);
        SendSms(from.CustomerPhone, "Transfer done");
        GeneratePdfReceipt(from, to, amount);
    }
}

After SOLID — production design

// ✅ SRP — each class one reason to change
public sealed class TransferOrchestrator {
    private readonly ITransferValidator _validator;
    private readonly ILedgerService _ledger;
    private readonly IFraudChecker _fraud;
    private readonly INotificationService _notify;

    public async Task<Result> ExecuteAsync(TransferRequest req, CancellationToken ct) {
        await _validator.ValidateAsync(req, ct);
        await _fraud.CheckAsync(req, ct);
        await _ledger.PostAsync(req, ct);
        await _notify.SendTransferConfirmationAsync(req, ct);
        return Result.Success();
    }
}

Outcome

Deployment frequency for transfer module increased 4x; unit test count from 12 to 89 isolated tests.

SOLID in ASP.NET Core — Repository Refactoring

Register abstractions in Program.cs as Scoped. Keep controllers thin — delegate to MediatR handlers or application services. ShopNest Clean Architecture: Domain → Application → Infrastructure → Api.

builder.Services.AddScoped<IOrderService, OrderService>();
builder.Services.AddMediatR(cfg => cfg.RegisterServicesFromAssembly(typeof(PlaceOrderHandler).Assembly));

SOLID and design patterns

SRP enables focused classes; OCP pairs with Strategy and Factory; LSP guards inheritance; ISP splits fat interfaces; DIP powers DI and Repository pattern. SOLID is the foundation — patterns are the tools.

Unit testing with SOLID

var mock = new Mock<IOrderRepository>();
mock.Setup(r => r.GetAsync(1, default)).ReturnsAsync(new Order(1, 100m));
var handler = new GetOrderHandler(mock.Object);
var result = await handler.Handle(new GetOrderQuery(1), default);
Assert.Equal(100m, result.Total);

Pattern recognition

God class → SRP split. if/else feature growth → OCP Strategy. Broken subclass → LSP composition. Fat interface → ISP split. new Concrete() → DIP + DI. Legacy monolith → strangler fig refactor.

Refactoring notes

Always add characterization tests before extracting classes. Use the strangler fig pattern — route new features to refactored modules while legacy code remains until migrated.

Common errors & fixes

• God classes with 10+ responsibilities (SRP violation) — Extract focused services — one reason to change per class.
• Adding if/else chains for every new feature (OCP violation) — Use Strategy or Factory; extend via new classes, not edits.
• Subclass throws NotImplementedException (LSP violation) — Prefer composition and role-specific interfaces over broken inheritance.
• Controllers new-ing concrete repositories (DIP violation) — Inject interfaces via constructor DI in ASP.NET Core.

Best practices

• 🟢 One reason to change per class (SRP)
• 🟢 Extend via new classes, not edits (OCP)
• 🟡 Introduce interfaces when you need test doubles or multiple implementations
• 🟡 Keep controllers thin — delegate to handlers/services
• 🔴 Never skip characterization tests before legacy refactors
• 🔴 Register all abstractions in Program.cs — avoid service locator anti-pattern

Interview questions

Fresher level

Q1: What is Repository Refactoring and which SOLID letter does it relate to?
A: Repository Refactoring maps to SOLID on ShopNest Authentication. Explain the principle in one sentence, then give a before/after code example.

Q2: Explain SRP with a real example.
A: Split god classes — TransferService becomes validator, ledger, fraud checker, notifier. One reason to change per class.

Q3: OCP vs inheritance — when is inheritance wrong?
A: When subclasses break base behavior (LSP). Prefer Strategy/Factory for extension without modification.

Mid / senior level

Q4: How does DIP relate to ASP.NET Core DI?
A: Program.cs registers interfaces to implementations; controllers/handlers depend on abstractions only.

Q5: When should you NOT apply SOLID?
A: Throwaway prototypes, scripts, or 50-line utilities — apply when the module will grow or be team-owned.

Q6: How do you refactor legacy code safely?
A: Characterization tests first, extract interface, inject via DI, migrate callers incrementally (strangler fig).

Coding round

Refactor a god-class OrderService into SRP-compliant services with DI registration and one xUnit test using Moq.

public sealed class PlaceOrderHandler(IOrderRepository repo, INotifier notify)
{
    public async Task Handle(PlaceOrderCommand cmd, CancellationToken ct) {
        var order = Order.Create(cmd.Items);
        await repo.AddAsync(order, ct);
        await notify.SendAsync(order, ct);
    }
}

Summary & next steps

• Article 78: Repository Refactoring — Complete Guide
• Module: Module 8: Refactoring and Clean Code · Level: ADVANCED · Principle: SOLID
• Applied to ShopNest Clean Architecture — Authentication

Previous: Controller Refactoring — Complete Guide
Next: Dependency Injection Refactoring — Complete Guide

Practice: Refactor one small class using today's principle — commit with refactor(solid): article-78.

FAQ