Comment by Filip Milovanović on How to handle data-intensive functionality of domain objects in Clean Architecture?

"But that would break DDD" - DDD (and rich domain models in general) do not require the actual means of doing something (the ultimate underlying implementation that gets the job done) to be fully implemented within the domain layer code (or even by the same piece of software). Instead, you want to try and capture the domain logic (business rules) in your domain code, meaning the core code should be written in a way that expresses/enforces those rules - but it should absolutely delegate the low level details of that to layers below that invoke infrastructure code or external services.