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.

Thanks for your answer and this gives a new direction and another perspective to look at the current design.I think uniqueness at this point isn't a real constraint and certainly doesn't give competitive advantage nor is it a good economical trade-off. I think that validating the constraint at DB level (unique index) is suffcient and let that exception bubble up to the API exception handler. I also believe that my aggregate design was wrong because of the valid point about concurrent edits. Editing a user doesn't mean invariants of other users should be validated

JohnDoe
– JohnDoe

2019-01-16 09:31:25 +00:00
Commented Jan 16, 2019 at 9:31

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 »