we want our domain model to have no dependencies whatsoever. 1 We don’t want infrastructure concerns bleeding over into our domain model and slowing our unit tests or our ability to make changes. Instead, as discussed in the introduction, we’ll think of our model as being on the “inside,” and dependencies flowing inward to it; this is what people sometimes call onion architecture836 ↱
Architecture Patterns with Python
Enabling Test-Driven Development, Domain-Driven Design, and Event-Driven Microservices
Harry Percival, Bob Gregory