Design patterns·The shape of the whole application
there is one class per thing a user can do, with one public method, and its name is a verb.
Use case interactor
Also calledinteractor, use case object, command handler
An object encapsulating a single application use case, invoked by an adapter and orchestrating entities to carry it out. Making each use case its own class rather than a method on a large service means the dependencies of that one operation are declared precisely, and the class name is a readable inventory of what the system does. The cost is a great many small classes, which some teams find clarifying and others find noise.