Payment strategy pattern in LLD - Scalability & System Analysis

Scalability Analysis - Payment strategy pattern

Growth Table: Payment Strategy Pattern

Users	Payment Methods	Transactions/sec	System Complexity	Latency
100	2-3	~10	Simple strategy selection	Low
10,000	5-10	~1,000	More strategies, caching payment configs	Moderate
1,000,000	10-20	~100,000	Distributed strategy execution, async processing	Higher, needs optimization
100,000,000	20+	~10,000,000	Microservices, sharded payment services, global load balancing	Critical to optimize

First Bottleneck

The first bottleneck is the payment processing service that executes the strategy logic. As user transactions grow, the CPU and memory on servers handling payment strategies get overwhelmed. Also, the database storing payment configurations and transaction records becomes a bottleneck due to increased read/write operations.

Scaling Solutions

• Horizontal scaling: Add more servers running payment strategy services behind a load balancer to distribute transaction load.
• Caching: Cache payment method configurations to reduce database hits.
• Asynchronous processing: Use message queues to handle payment execution asynchronously for non-blocking user experience.
• Database optimization: Use read replicas and connection pooling to handle increased queries.
• Sharding: Partition transaction data by user region or payment method to reduce contention.
• Microservices: Separate payment strategies into independent services for better maintainability and scaling.

Back-of-Envelope Cost Analysis

At 1M users with 100K transactions/sec:

• Each server handles ~5,000 concurrent connections -> Need ~20 servers.
• Database handles ~100,000 QPS -> Use read replicas and sharding.
• Bandwidth: Assuming 1KB per transaction -> 100MB/s network bandwidth needed.
• Storage: 100K transactions/sec x 100 bytes/transaction x 3600 sec = ~36GB/hour.

Interview Tip

Start by explaining the payment strategy pattern and its role in flexibility. Then discuss how load grows with users and transactions. Identify the first bottleneck (processing and DB). Propose scaling solutions step-by-step: caching, horizontal scaling, async processing, and database optimizations. Use real numbers to show understanding of system limits.

Self Check

Your database handles 1000 QPS. Traffic grows 10x to 10,000 QPS. What do you do first?

Answer: Add read replicas and implement caching to reduce direct database load before scaling application servers.

Key Result

The payment strategy pattern scales well initially but the payment processing service and database become bottlenecks as transactions grow. Horizontal scaling, caching, async processing, and database sharding are key to handle millions of users and transactions.

Practice

1. What is the main benefit of using the Payment Strategy Pattern in a payment system?

easy

A. It allows switching between different payment methods without changing the main code.

B. It forces all payment methods to use the same currency.

C. It stores all payment data in a single database table.

D. It encrypts payment information automatically.

Solution

1. Step 1: Understand the purpose of the Payment Strategy Pattern

   The pattern is designed to let the system switch payment methods easily without modifying the main logic.

2. Step 2: Analyze the options

   Only It allows switching between different payment methods without changing the main code. describes this benefit correctly. Other options describe unrelated features.

3. Final Answer:

   It allows switching between different payment methods without changing the main code. -> Option A

4. Quick Check:

   Payment Strategy Pattern = Switch payment methods easily [OK]

Hint: Focus on flexibility to switch payment methods without code changes [OK]

Common Mistakes:

• Confusing strategy pattern with data storage or encryption
• Thinking it enforces currency or database rules
• Assuming it handles security automatically

2. Which of the following is the correct way to define a payment strategy interface in a typical object-oriented language?

easy

A. interface PaymentStrategy { void pay(double amount); }

B. class PaymentStrategy { void pay(amount); }

C. function PaymentStrategy(amount) { return pay; }

D. var PaymentStrategy = pay => amount;

Solution

1. Step 1: Identify the correct syntax for an interface

   In object-oriented languages, interfaces declare method signatures without implementation. interface PaymentStrategy { void pay(double amount); } uses 'interface' and a method signature correctly.

2. Step 2: Check other options

   class PaymentStrategy { void pay(amount); } is a class, not an interface. Options C and D use function syntax, not interface definitions.

3. Final Answer:

   interface PaymentStrategy { void pay(double amount); } -> Option A

4. Quick Check:

   Interface syntax = interface PaymentStrategy { void pay(double amount); } [OK]

Hint: Look for 'interface' keyword and method signature format [OK]

Common Mistakes:

• Using class instead of interface for strategy definition
• Confusing function syntax with interface
• Missing method parameter types

3. Given the following code snippet implementing the Payment Strategy Pattern, what will be the output?

class PaymentStrategy {
  pay(amount) { throw 'Not implemented'; }
}

class CreditCardPayment extends PaymentStrategy {
  pay(amount) { return `Paid ${amount} with Credit Card`; }
}

class PayPalPayment extends PaymentStrategy {
  pay(amount) { return `Paid ${amount} with PayPal`; }
}

class PaymentContext {
  constructor(strategy) { this.strategy = strategy; }
  executePayment(amount) { return this.strategy.pay(amount); }
}

const context = new PaymentContext(new PayPalPayment());
console.log(context.executePayment(100));

medium

A. Paid 100 with Credit Card

B. Not implemented

C. Paid 100 with PayPal

D. Error: strategy.pay is not a function

Solution

1. Step 1: Trace the object creation and method calls

   The PaymentContext is created with a PayPalPayment strategy. Calling executePayment(100) calls PayPalPayment's pay method.

2. Step 2: Understand the pay method output

   PayPalPayment's pay returns 'Paid 100 with PayPal'. This string is printed.

3. Final Answer:

   Paid 100 with PayPal -> Option C

4. Quick Check:

   Context uses PayPalPayment = Output with PayPal [OK]

Hint: Check which strategy instance is passed to context [OK]

Common Mistakes:

• Assuming default or CreditCardPayment is used
• Expecting an error from base class
• Confusing method override behavior

4. Identify the error in the following Payment Strategy Pattern implementation:

class PaymentStrategy {
  pay(amount) { console.log('Paying ' + amount); }
}

class BitcoinPayment extends PaymentStrategy {
  pay() { console.log('Paying with Bitcoin'); }
}

const payment = new BitcoinPayment();
payment.pay(50);

medium

A. PaymentStrategy should not have a pay method implementation.

B. BitcoinPayment's pay method does not accept the amount parameter.

C. BitcoinPayment should not extend PaymentStrategy.

D. Calling pay with 50 causes a syntax error.

Solution

1. Step 1: Compare method signatures in base and subclass

   PaymentStrategy's pay expects an amount parameter, but BitcoinPayment's pay method does not accept any parameters.

2. Step 2: Understand the impact of signature mismatch

   Calling payment.pay(50) passes an argument, but BitcoinPayment's pay ignores it, causing unexpected behavior or errors.

3. Final Answer:

   BitcoinPayment's pay method does not accept the amount parameter. -> Option B

4. Quick Check:

   Method signature mismatch = BitcoinPayment's pay method does not accept the amount parameter. [OK]

Hint: Check if subclass methods match base method parameters [OK]

Common Mistakes:

• Thinking base class should not implement pay
• Assuming inheritance is wrong
• Confusing runtime error with syntax error

5. You are designing a payment system that must support credit cards, PayPal, and a new cryptocurrency payment method. Using the Payment Strategy Pattern, which design approach best supports adding the new method with minimal changes?

hard

A. Use a global variable to switch payment methods inside the main payment function.

B. Modify the existing CreditCardPayment class to handle cryptocurrency payments.

C. Add cryptocurrency payment logic inside the PaymentContext class directly.

D. Create a new class implementing the PaymentStrategy interface for cryptocurrency and pass it to the payment context.

Solution

1. Step 1: Understand the open/closed principle in design

   The system should be open for extension but closed for modification. Adding a new payment method should not require changing existing classes.

2. Step 2: Evaluate each option

   Create a new class implementing the PaymentStrategy interface for cryptocurrency and pass it to the payment context. creates a new class implementing the interface, fitting the pattern and minimizing changes. Options B and C modify existing classes, violating the principle. Use a global variable to switch payment methods inside the main payment function. uses a global variable, which is poor design.

3. Final Answer:

   Create a new class implementing the PaymentStrategy interface for cryptocurrency and pass it to the payment context. -> Option D

4. Quick Check:

   New class for new method = Create a new class implementing the PaymentStrategy interface for cryptocurrency and pass it to the payment context. [OK]

Hint: Add new payment as new class, avoid changing existing code [OK]

Common Mistakes:

• Modifying existing payment classes
• Adding logic inside context class
• Using global variables for strategy switching