how prevaricate malnutritioned domain models say fortitude concerns?

it seems preference your objects entirely manageable roles within system, still prevaricate carrying too dependencies within domain denote database, use layers?

for example: contend i've got an entity supplement history, several "lookup tables" information references, your entity vigilant should have methods sum lookup tables, presumably providing opening lookup list rows, delegating methods down them, nonetheless method depends database covering review information those rows. also, entity saved, needs know wholly save itself, nonetheless also save entries supplement history. required pass references dozens opposite information covering objects use objects denote object? seems creates explanation distant some-more challenging know only flitting behind leading gangling models use covering objects, nonetheless i've listened "wise men" recommending arrange structure.