Which class best follows Single Responsibility in a payments module?

Problem Statement

Explanation

A focused class is easier to change and test. If its reason to change is “how we charge,” it stays cohesive and stable. Auxiliary work like email or invoicing belongs to separate collaborators invoked by higher-level flows.

Code Solution

SolutionRead Only

class ChargeProcessor{ charge(req:ChargeRequest): ChargeResult }

Practice Sets

This question appears in the following practice sets:

Low-Level Design (LLD) Interview Core

Next Question

Master Interviews
Anywhere, Anytime

Which class best follows Single Responsibility in a payments module?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews Anywhere, Anytime

Which class best follows Single Responsibility in a payments module?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews
Anywhere, Anytime