Adapter Design Pattern in .NET

The Adapter pattern converts the interface of a class into another interface the client expects. It allows incompatible interfaces to work together without modifying existing code.

 

Purpose

To enable integration between systems or components with mismatched interfaces by translating one interface to another.

 

Key Characteristics

  • Acts as a bridge between incompatible interfaces
  • Promotes reusability of existing components
  • Often used when integrating third-party services

 

Pros

  • Supports integration with legacy or external systems
  • Avoids rewriting existing code
  • Promotes flexibility and modularity

 

Cons

  • Adds an extra layer of abstraction
  • Overuse can lead to complex system dependencies

 

Use Cases

  • Adapting a third-party payment gateway into a common interface
  • Converting external logging systems to your internal logger
  • Integrating legacy financial APIs into modern interfaces

 

Real-Time Finance Example: Adapting a Third-Party Payment Gateway

Suppose your app expects a common IPaymentProcessor interface, but a third-party provider (e.g., RazorPay) exposes a different interface. You can use an Adapter to plug it into your system.

 

1. Expected Target Interface

public interface IPaymentProcessor

{

    void Pay(decimal amount);

}

 

2. Existing Third-Party Class (Incompatible Interface)

public class RazorPayGateway

{

    public void MakePayment(decimal value)

    {

        Console.WriteLine($"Payment of ₹{value} processed via RazorPay.");

    }

}

 

3. Adapter Implementation

public class RazorPayAdapter : IPaymentProcessor

{

    private readonly RazorPayGateway _razorPay;

 

    public RazorPayAdapter(RazorPayGateway razorPay)

    {

        _razorPay = razorPay;

    }

 

    public void Pay(decimal amount)

    {

        _razorPay.MakePayment(amount); // adapting call

    }

}

 

4. Client Code Usage

class Program

{

    static void Main()

    {

        RazorPayGateway thirdParty = new RazorPayGateway();

        IPaymentProcessor paymentProcessor = new RazorPayAdapter(thirdParty);

 

        paymentProcessor.Pay(999.99m);

    }

}

 

Output

Payment of ₹999.99 processed via RazorPay.

 

Summary

  • Adapter Pattern is essential for integrating third-party or legacy systems
  • Helps maintain a clean, consistent interface in your application
  • Perfect for finance applications dealing with different APIs or services (payment, logging, tax, etc.)

Comments

Post a Comment

Popular posts from this blog

Multiline to singleline IN C# - CODING

Multiline to singleline IN C# - CODING using System; using System.Linq; class Program {     static void Main(string[] args)     {         string input = @"This is                  multiline";                  // Split the input into lines, trim each line, and filter out empty lines         string result = string.Join(" ", input.Split(new[] { '\r', '\n' }, StringSplitOptions.RemoveEmptyEntries)                                                .Select(line => line.Trim()));         Console.WriteLine(result);     } } Output: This is  multiline
Read more

EF Core interview questions for beginners

1. What is Entity Framework Core (EF Core)? EF Core is an open-source Object-Relational Mapper (ORM) that enables .NET developers to work with databases using .NET objects. It allows you to interact with a database using strongly typed classes and LINQ queries, rather than writing raw SQL queries. EF Core supports various database providers, such as SQL Server, SQLite, PostgreSQL, MySQL, and more. 2. What are the advantages of using EF Core over traditional ADO.NET? Productivity:  EF Core allows you to work with databases using high-level objects, reducing the amount of boilerplate code you need to write. Cross-platform:  EF Core supports multiple databases and works on Windows, Linux, and macOS. LINQ Support:  You can query the database using LINQ, which is more type-safe and easier to maintain than raw SQL queries. Code-First & Database-First:  EF Core supports both approaches to model databases. Change Tra...
Read more

EF Core interview questions for experienced

EF Core interview questions for experienced 1. What are the main differences between Entity Framework (EF) and Entity Framework Core (EF Core)? EF Core is a complete rewrite of EF. Unlike EF, EF Core supports cross-platform development, improved performance, LINQ query translation, and has a more modular architecture. EF Core does not support all features that EF 6 does (like lazy loading and some database providers). 2. How does EF Core handle migrations, and what are some common pitfalls? EF Core uses migrations to update the database schema based on model changes. Common pitfalls include not applying migrations correctly, misalignment between model and database state, or missing/overwriting migrations during collaboration in a team environment. 3. Explain the difference between Add and Attach methods in EF Core. Add method is used to add a new entity to the context and mark it as Added , while Attach attaches an existing entity to the context with no changes. The Attach meth...
Read more