How to determine when a class or module performs too many functions and violates the single responsibility principle?

The Single Responsibility Principle states that a class or module should have only one reason to change, meaning it should perform a single function.

Signs of violation:

• The class contains many methods that are not related to each other in meaning.
• The class mixes different levels of abstraction (for example, business logic and database operations).
• It is difficult to understand what the class is responsible for without detailed study.
• When requirements change, it is often necessary to modify the same class for different reasons.

If you see that a class is growing and starting to perform functions that can be separated into different classes (for example, data processing, logging, network interaction), it is worth splitting it.

Example: a class that reads data from a database, formats it for output, and logs errors — it is better to split into three classes with separate responsibilities.