Timeline for Which layer for custom type (DDD)
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 2, 2018 at 14:47 | comment | added | Constantin Galbenu | @R.Gomez That control library that controls a physical device should stay in the infrastructure. You need to be careful to split the business behavior (the DDD kind of behavior) from the low-level IO functions. The applications that control physical devices are a special case where DDD does not apply 100% because they contain a lot of infrastructure logic. | |
| Jan 2, 2018 at 14:40 | comment | added | R. Gomez | and what about referencing libraries in my DL project? For example in my specific case some of my domain models (I think they are more value objects...I'm still learning DDD :P) are measure devices, and for them I wrote a control Library that contains the BL to control the devices. So DDD's "behaviour" of this classes resides in a 3rd-party lib (under my control), so I need them to build my domain....or I'm overseeing/missunderstanding sth? | |
| Jan 2, 2018 at 14:36 | comment | added | Constantin Galbenu | It is ok to reference Domain Objects (aggregates, value objects) from any other layer. | |
| Jan 2, 2018 at 14:31 | comment | added | R. Gomez |
I also think about this, but then I'll need a reference to my domain model EVERY time I want to declare some field, prop or something as range. So at the end I'll be referencing directly my DL in all my layers (apart from UI). And that's it's something that makes me feel strange...
|
|
| Jan 2, 2018 at 13:09 | history | answered | Constantin Galbenu | CC BY-SA 3.0 |