Document how we've used domain driven design

[junlarsen]

Quite a bit of yapping but it should give beginners an idea of why we do it, how it's useful, and how we implement it

[linear]

DOT-658 Document domain-driven-design/architectural choices

[hanlun0804]

I think it was a nice introduction, some yapping is nice when you go from not knowing what it is :)

[henrikskog]

Looking good! I would like a lot more examples, but this is something we can iterate on going forward

[henrikskog]

It would be nice to include some examples of the patterns we follow in repositories and services. For example, when a delete method in a repository returns null, it means that there was no such resource to delete. This sort of stuff is important to document I think, as we are making these rules ourselves.

(delete example may not be entirely correct, but I hope I get my point across)

[junlarsen]

I agree we should add stuff about "return null" and other paradigms we've used, but I think they are probably better fit in another document

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
invoicification	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 4, 2024 3:36pm