DDD/"hexagonal architecture" insist on separating the domain, aka model, from infrastructure requirements. This looks clean and logical until you realize that storing your domain object in memory might hurt performance if the domain object happens to be too large, and even more so fetching such domain object from persistent storage/network.
The proposed "cure" which I have seen, is centered around defining the aggregates to be "small" and around "eventual consistency". Both seem to delegate the business rules to stateless ("domain") services and not the aggregates (domain entities) behaviour. So this appears to favour the creation of "anemic domain objects"; however "rich domain objects" seems to me the main purpose of DDD (together with the creation of the ubiquitous domain language).
What you, as a DDD practitioner, think of this concern? (I am not currently a DDD practitioner, but given the hype around "microservices", I might perhaps become one).