Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Per DDD/Eric Evans, aren’t I supposed to use 1 repository per Aggregrate Root?

keelerjr12
– keelerjr12

2018-04-13 10:49:53 +00:00
Commented Apr 13, 2018 at 10:49
@keelerjr12 Typically yes. But that doesn't mean you can't or won't have multiple aggregate roots in your design. My proposal is based on the fact that Entry is treated as an aggregate root. I don't know the very specifics of your application but in your scenario I think an Entry needs to be treated as such because (logically) there will be more than one cases when you want to access it outside the Journal aggregate.

dpant
– dpant

2018-04-13 11:39:06 +00:00
Commented Apr 13, 2018 at 11:39

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »