Thoughts for the docs #7
Description
-> makes the code harder to read, why do I want that?
-> validation before, if an error occurs, everything is rolled back
-> holiday signal lives on holiday, holidayCreatedEvent would live on holiday
-> some command -> event -> command hops feel superfluous, what is the best pattern? What trade-offs are there?
-> Handlers are functional with defined input and output. This can be ideally unittested if I were to do this.
-> Validation imperative in the view layer (API or view)
-> All cross-app/domain concerns should run via events
-> Do not persist things in the DB that live in another app/domain
-> Traceability is hard, debugger doesn't help either. I've already considered whether to parse the code via AST and write a table and then visualise it as a directed graph using a tool?
-> Why custom events and letting django signals? Because then you think in models. That's not good.