Timeline for Help understanding modeling in domain-driven design
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2015 at 20:01 | vote | accept | Zack | ||
| Aug 30, 2015 at 20:01 | vote | accept | Zack | ||
| Aug 30, 2015 at 20:01 | |||||
| Aug 29, 2015 at 17:38 | answer | added | Erik Eidt | timeline score: 3 | |
| Aug 28, 2015 at 15:41 | comment | added | Zack | @Tom: I thought so, updated my question with what I originally thought, based upon your reply. | |
| Aug 28, 2015 at 15:41 | comment | added | Zack | I guess one thing that confused me about the Vernon's essay was what appeared to be an entity and an aggregate combined. Are they/can they be the same thing (depending upon the domain)? | |
| Aug 28, 2015 at 15:39 | history | edited | Zack | CC BY-SA 3.0 |
Slight image change.
|
| Aug 28, 2015 at 15:23 | comment | added | Tom | I often have services which I call from controllers, and then use the entity framework as the model layer. I wouldn't have description as its own table. I'd keep it simple until you get problems and then refactor to keep it clean. Don't over complicating it initially. | |
| Aug 28, 2015 at 14:41 | history | edited | Zack | CC BY-SA 3.0 |
[Edit removed during grace period]
|
| Aug 28, 2015 at 4:37 | review | First posts | |||
| Aug 28, 2015 at 5:56 | |||||
| Aug 28, 2015 at 4:32 | history | asked | Zack | CC BY-SA 3.0 |