News for hackers. Stuff that matters.
Re:Software Architecture Patterns: 5 minute read by DenisM on Thursday October 28, 2021 @11:13AM (#29027060)
> So you create a class in the Domain which is responsible to save the domain object?

Yes.

> Is that not a forbidden by the layer principle because now the domain model layer has a dependency to the persistency layer.

In my book it's fine. I find that in practice one-way dependencies are ok, so domain->persistence dependency is fine so long as there is no persistence->domain dependency. Simply avoiding loops will take you a very long way.

Re:Software Architecture Patterns: 5 minute read by kenniskrag on Thursday October 28, 2021 @11:18AM (#29027115)
> In my book

Which book?

I see know that one can think of the domain model as most changed layer and if there is a bigger change it is because the domain model changes (e.g. business requirements). So a dependency from the domain model to other parts below are mostly fine.

Re:Software Architecture Patterns: 5 minute read by 5e92cb50239222b on Thursday October 28, 2021 @11:20AM (#29027145)
> Which book?

I believe it's used as an idiom.

https://dictionary.cambridge.org/us/dictionary/english/in-my...

Re:Software Architecture Patterns: 5 minute read by myohmy on Thursday October 28, 2021 @02:52PM (#29029960)
You are technically correct, the best kind of correct.
Re:Software Architecture Patterns: 5 minute read by DenisM on Thursday October 28, 2021 @11:24AM (#29027184)
indeed