Is it correct to separate the business logic into class modules?

[JuTiger-Lee]

Is it correct to configure a class with only business logic as a separate module like a user module?

[Sairyss]

What is your use case? Hard to tell without more details.
Any business logic needs to be accessed somehow, or access the database, so you will probably need to add some non-business logic code to your module (for example, add a controller, repository, etc.)

[JuTiger-Lee]

Thanks for the reply.
First, for example, is it okay to configure the logic of sending an email when logging in as a separate business logic module? The email sending logic makes a request to an external API, so there is an adapter, but there is no adapter requesting externally.

[Sairyss]

Sending email can be it's own module yes.
If I understood your use case correctly, you can do this, for example:

• You can create an Email module that sends emails of any kind and exposes some kind of public interface to send an email (a command). It should be a black box that does whatever you need (calls external API, in your case).
• When logging in, you can send an event like UserLoggedInEvent and make a listener like SendEmailWhenUserLoggedIn that will call an Email module on that event.

[JuTiger-Lee]

Thanks!