On microservices, should the use case call the another service? about clean-architecture-manga HOT 4 CLOSED

Hello @leandrofagundes,

I think it's definitely OK if it's part of the business logic (using some abstraction like IFriendlyService and implementing it in the infrastructure layer).

from clean-architecture-manga.

Every use case is piece of (isolated) business logic. So it can (and probably should) be combined if needed. However if you call IUseCase directly there could be difficulties with sharing (or not sharing) connections/transactions and other stuff. So i would implement special aggregator to accomplish this task. I can't answer how exactly without deep dive into concrete problem

from clean-architecture-manga.

Hi @qpippop thanks for participating,

so, thinking about a monolyth, where I have many modules and contexts.
If I need to run a rule from a specific module from another module, can one Use Case call another Use Case implementing it as a service or should all the rule about one use case be done inside itself?

from clean-architecture-manga.

Very nice explanation @qpippop. I totally agree :)

from clean-architecture-manga.