Is it possible to introduce external dependencies into the domain model?

Injecting external dependencies directly into the domain model is generally not recommended, as it violates the principles of clean architecture and encapsulation. The domain model should be independent of infrastructural details and external services to remain as clean and testable as possible.

Instead, external dependencies are injected into infrastructure layers or services that interact with the domain model through interfaces or abstractions. Domain objects should contain only business logic and data that do not depend on specific implementations of external services.

For example, if the domain model needs access to data, it is better to use the "Repository" pattern, which provides an interface for data operations, and the specific repository implementation is injected into services, not into domain entities.

Thus, injecting external dependencies into the domain model is undesirable to preserve its purity, portability, and ease of testing.