Dependency diagram (fig 7.7) confusing

[elafnit]

Fig 7.7 would benefit from using some UML notation for how the dependencies are implemented. The current diagram, at first glace, seems to indicate that the Application layer would have a dependency on the Infrastructure layer. There is indeed a relationship between the 2 layer; however, this should be indicated as an inversion of control where the Infrastructure layer implements an interface and injects the implementation. UML provides a connector standard that most developer should know to understand the type of relationship.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 95f3dcd7-3220-e9cf-3ca6-90b1282410ec
• Version Independent ID: 5a30bea5-326b-ea72-59ae-dfef1e190e4a
• Content: Designing a DDD-oriented microservice
• Content Source: docs/architecture/microservices/microservice-ddd-cqrs-patterns/ddd-oriented-microservice.md
• Product: dotnet-architecture
• Technology: microservices
• GitHub Login: @nishanil
• Microsoft Alias: nanil

[simonec]

I was almost to create the same issue, below the diagram from the "red book"