This is a very common anti-pattern when we think of the separation that must be performed on the application. Many engineers confuse the separation of components of the stack with the separation of the logic layer, and, with that, end up generating an anemic domain without any representation in the business.
In the following diagram, we can see this bad practice. The software is composed of three physical components that are not required. The separation of the application is extremely granular. In this diagram, the Orchestrator and DataAccess don't make sense.
The essential business needs to access the data. Soon, there will be no logic in creating this separation. Another point is that if the Orchestrator directly ...
