When NOT to Use Design Patterns — Complete Guide

Introduction

When NOT to Use Design Patterns — Complete Guide 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 when not to use design patterns with real banking, e-commerce, or SaaS examples — not toy animal demos. This article delivers production depth on Inventory.

After this article you will

• Explain When NOT to Use Design Patterns in plain English and in enterprise architecture terms
• Implement When NOT to Use Design Patterns in ShopNest Enterprise Architecture (Inventory)
• Compare anti-pattern vs production-ready pattern implementation
• Answer fresher and senior design pattern interview questions confidently
• Connect this lesson to Article 67 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 65 — How Senior Developers Use Design Patterns — Complete Guide
• Time: 24 min reading + 30–45 min hands-on

Concept deep-dive

Level 1 — Analogy

Patterns are tools, not trophies — a junior with 12 patterns often ships slower than one with clear functions.

Level 2 — Technical

When NOT to Use Design Patterns builds architectural judgment — when patterns help vs hurt, how TCS/Infosys lateral interviews probe trade-offs on Inventory.

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 — Inventory

Implement When NOT to Use Design Patterns in C# for Inventory: 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 — When NOT to Use Design Patterns on ShopNest (Inventory)
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

// When NOT to Use Design Patterns
// Judgment: pattern cost vs benefit on ShopNest Inventory

Real-World Example 1 — ERP Inventory Module

MANDATORY: Enterprise-grade When NOT to Use Design Patterns implementation in a production erp inventory module.

Business requirement

Warehouse stock levels sync across manufacturing, procurement, and sales channels — stale data causes overselling and production delays.

Why When NOT to Use Design Patterns is needed

Without When NOT to Use Design Patterns, the ERP Inventory Module team at ShopNest faces tight coupling, untestable code, and painful refactors every sprint. When NOT to Use Design Patterns decouples responsibilities so the Inventory module can evolve independently while meeting scalability and compliance requirements.

Architecture

[Client/API] → [When NOT to Use Design Patterns Abstraction]
  → [ShopNest.Inventory Service] → [EF Core / Redis / Message Bus]
  → [Downstream: Audit, Notifications, Reporting]

Tech stack: ASP.NET Core Web API, EF Core, Redis distributed cache, background hosted services

Full working code

// REAL-WORLD EXAMPLE 1: ERP Inventory Module
// ShopNest Enterprise Architecture — Inventory module
// Pattern: When NOT to Use Design

namespace ShopNest.Architecture.Inventory;

public interface IWhenNOTtoUseDesignService
{
    Task ExecuteAsync(WhenNOTtoUseDesignRequest request, CancellationToken ct = default);
}

public sealed class ERPInventoryModuleWhenNOTtoUseDesignService : IWhenNOTtoUseDesignService
{
    private readonly ILogger _logger;

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

    public async Task ExecuteAsync(WhenNOTtoUseDesignRequest request, CancellationToken ct)
    {
        _logger.LogInformation("[When NOT to Use Design] Processing {Domain} request {Id}",
            "ERP Inventory Module", 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 IWhenService in xUnit tests
• Scalable — horizontal scaling of Inventory workers under load
• Maintainable — new business rules added via new classes, not if-else chains

Real-World Example 2 — HRMS Payroll Processing

MANDATORY: Second complete example in a different domain — HRMS Payroll Processing.

Business problem

Payroll runs involve tax rules, attendance, benefits, and approvals — business rules change every fiscal year and vary by region.

Why When NOT to Use Design Patterns solves it

In HRMS Payroll Processing, Indian IT delivery teams (TCS, Infosys, Wipro lateral rounds) frequently ask how When NOT to Use Design Patterns 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: HRMS Payroll Processing
// ShopNest Enterprise Architecture — Inventory module
// Pattern: When NOT to Use Design

namespace ShopNest.Architecture.Inventory;

public interface IWhenNOTtoUseDesignService
{
    Task ExecuteAsync(WhenNOTtoUseDesignRequest request, CancellationToken ct = default);
}

public sealed class HRMSPayrollProcessingWhenNOTtoUseDesignService : IWhenNOTtoUseDesignService
{
    private readonly ILogger _logger;

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

    public async Task ExecuteAsync(WhenNOTtoUseDesignRequest request, CancellationToken ct)
    {
        _logger.LogInformation("[When NOT to Use Design] Processing {Domain} request {Id}",
            "HRMS Payroll 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 HRMS 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 When NOT to Use Design Patterns abstractions in Program.cs with appropriate lifetimes — Singleton for stateless, Scoped for request-bound, Transient for lightweight factories.

Microservices: Apply When NOT to Use Design Patterns within bounded contexts — each ShopNest service (Inventory) owns its implementation.

Pattern comparison & when NOT to use

Compare When NOT to Use Design Patterns 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 WhenNOTtoUseDesignPatternsPatternTests
{
    [Fact]
    public async Task ExecuteAsync_ReturnsSuccess()
    {
        var mock = new Mock<IWhenNOTtoUseDesignPatternsService>();
        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.

Architectural judgment

Senior interviewers reward trade-off analysis over pattern name-dropping. Always answer: problem → options → chosen pattern → alternatives rejected → metrics you'd monitor.

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 When NOT to Use Design Patterns pattern and when would you use it?
A: When NOT to Use Design Patterns solves a specific recurring problem on ShopNest Inventory. Explain intent, structure (participants), and one real example — then state when NOT to use it.

Q2: When NOT to Use Design Patterns 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 When NOT to Use Design Patterns for ShopNest Inventory: interface, concrete class, DI registration, and xUnit test with Moq.

builder.Services.AddScoped<IWhenNOTtoUseDesignPatternsService, WhenNOTtoUseDesignPatternsService>();

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

Summary & next steps

• Article 66: When NOT to Use Design Patterns — Complete Guide
• Module: Module 8: Interview & System Design · Level: INTERMEDIATE · Type: INTERVIEW
• Applied to ShopNest Enterprise Architecture — Inventory

Previous: How Senior Developers Use Design Patterns — Complete Guide
Next: Overengineering Problems in Enterprise Applications — Complete Guide

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

FAQ