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 patterns, enterprise architecture, microservices, ASP.NET Core integration, and senior interview preparation. Every article includes minimum 2 mandatory real-world examples in different business domains.

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 two mandatory enterprise examples 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 Platform (Inventory)
• Compare the wrong approach vs the production-ready enterprise approach
• Answer fresher, mid-level, and senior design pattern interview questions confidently
• Connect this lesson to Article 67 and the 69-article Design Patterns roadmap

Prerequisites

• Software: .NET 8 SDK, VS 2022 or VS Code, SQL Server Express / LocalDB
• Knowledge: C# basics
• 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

When NOT to Use Design Patterns on ShopNest Enterprise Architecture is like adding a proven blueprint to a growing platform — clear boundaries keep teams productive.

Level 2 — Technical

When NOT to Use Design Patterns integrates with the LINQ query layer: write queries against IEnumerable or IQueryable, understand deferred execution, project to DTOs for ShopNest Enterprise Architecture reports. On ShopNest Enterprise Architecture this powers Inventory without coupling UI to database internals.

Level 3 — Architecture

[Browser] → [HTTPS/Kestrel] → [Middleware Pipeline]
  → [Routing] → [Controller Action] → [Service Layer]
  → [EF Core / Identity] → [Razor View Engine] → [HTML Response]

Project structure

ShopNest Enterprise Architecture/
├── 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

Step-by-Step Implementation — ShopNest (Inventory)

Follow the prompt template: create project → core classes → interfaces → pattern implementation → client code → run → enterprise refactor.

Step 1 — The wrong way

// ❌ BAD — fat controller, no ViewModel, sync DB call
public IActionResult Index()
{
    return _context.Products.Find(id); // sync, exposes entity, no auth
}

Step 2 — The right way

// ✅ CORRECT — When NOT to Use Design Patterns on ShopNest (Inventory)
var results = await _context.Products
    .Where(p => p.IsPublished && p.CategoryId == categoryId)
    .OrderBy(p => p.Name)
    .Select(p => new ProductReportDto { Id = p.Id, Name = p.Name, Revenue = p.Orders.Sum(o => o.Total) })
    .ToListAsync(ct);

Step 3 — Apply When NOT to Use Design Patterns

// When NOT to Use Design Patterns — ShopNest layered architecture
// ShopNest.Application → ShopNest.Infrastructure → ShopNest Enterprise Architecture

dotnet run --project ShopNest.Api
# Verify When NOT to Use Design Patterns pattern registration and integration tests pass

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# 12 implementations use primary constructors, records, and DI. Register pattern 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 (Orders, Payments, Inventory) owns its pattern 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.

Common errors & fixes

🔴 Mistake 1: Fat controllers with EF Core queries inline
✅ Fix: Move data access to services/repositories; keep controllers thin.

🔴 Mistake 2: Calling .ToList() too early materializing millions of rows into memory
✅ Fix: Defer execution — build IQueryable pipeline, then ToListAsync() once at the end.

🔴 Mistake 3: Filtering in memory after .ToList() instead of in the database query
✅ Fix: Keep filters in IQueryable, use Select projection, paginate with Skip/Take before materialization.

🔴 Mistake 4: Hard-coding connection strings in controllers
✅ Fix: Use appsettings.json + User Secrets locally; Azure Key Vault in production.

Best practices

• 🟢 Use async/await end-to-end for database and I/O calls
• 🟢 Register DbContext as Scoped; avoid capturing it in singletons
• 🟡 Use IQueryable until the last moment; avoid multiple enumeration; project with Select before ToList
• 🟡 Prefer method syntax for complex chains; use query syntax for joins when readability wins
• 🔴 Log structured data with Serilog — include OrderId, UserId, not passwords
• 🔴 Use HTTPS, secure cookies, and authorization policies in production

Interview questions

Fresher level

Q1: What is When NOT to Use Design Patterns in ASP.NET Core MVC?
A: When NOT to Use Design Patterns is a core MVC capability used in ShopNest Enterprise Architecture for Inventory. Explain in one sentence, then describe controller/view/service placement.

Q2: How would you implement When NOT to Use Design Patterns on a TCS-style delivery project?
A: Deferred execution, IQueryable pipelines, Select projection, Skip/Take pagination, and SQL logging in development.

Q3: IEnumerable vs IQueryable — when to use which?
A: IEnumerable for in-memory collections; IQueryable for EF Core database queries that translate to SQL.

Mid / senior level

Q4: Explain LINQ deferred execution and query translation briefly.
A: LINQ → Expression Tree → IQueryProvider → SQL (EF) or Iterator (in-memory) → Results.

Q5: Common production mistake with this topic?
A: Skipping validation, exposing secrets in Git, or untested edge cases (null model, unauthorized user).

Q6: .NET LINQ vs SQL — when to push logic to database?
A: Core is cross-platform, faster, cloud-ready; Framework is maintenance mode on Windows/IIS.

Coding round

Implement When NOT to Use Design Patterns for ShopNest Inventory: show interface, concrete class, DI registration, and xUnit test with mock.

public class WhenNOTtoUseDesignPatternTests
{
    [Fact]
    public async Task ExecuteAsync_ReturnsSuccess()
    {
        var mock = new Mock();
        mock.Setup(s => s.ExecuteAsync(It.IsAny(), default))
            .ReturnsAsync(Result.Success("test-id"));
        var result = await mock.Object.ExecuteAsync(new Request("test-id"));
        Assert.True(result.IsSuccess);
    }
}

Summary & next steps

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

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

Practice: Add one small feature using today's pattern — commit with feat(design-patterns): article-66.

FAQ