This shows you the differences between two versions of the page.
is_there_any_situation_where_dci_isn_t_appropriate_to_use [2014/01/19 23:09] gazoot created |
is_there_any_situation_where_dci_isn_t_appropriate_to_use [2014/04/07 08:19] (current) gazoot Added CRUD example |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Is there any situation where DCI isn't appropriate to use? ====== | ====== Is there any situation where DCI isn't appropriate to use? ====== | ||
- | Simple operations that are atomic and scoped to an object don't need DCI. It works best with system operations involving multiple objects. | + | Operations that are atomic and scoped to an object don't need DCI, for example simple [[https://en.wikipedia.org/wiki/Create,_read,_update_and_delete|CRUD]] functionality. DCI works best with system operations involving multiple objects. |
+ | |||
+ | See for example how the [[http://www.amazon.com/Lean-Architecture-Agile-Software-Development/dp/0470684208/ref=sr_1_1_bnp_1_pap?s=books&ie=UTF8&qid=1390152840&sr=1-1&keywords=lean+architecture+for+agile+software+development|Lean Architecture book]] distinguishes between Atomic Event Architectures and DCI architectures. | ||
+ | |||
+ | Another case is if the Context is very simple. For example, if your analysis shows that there is only one RoleMethod per Role, it suggests that in this case Roles don't have much expressive power. A simple procedural version would be much more readable then - and readability is the goal here. | ||
- | For one scimitar, see how the [[http://www.amazon.com/Lean-Architecture-Agile-Software-Development/dp/0470684208/ref=sr_1_1_bnp_1_pap?s=books&ie=UTF8&qid=1390152840&sr=1-1&keywords=lean+architecture+for+agile+software+development|Lean Architecture book]] distinguishes between Atomic Event Architectures and DCI architectures. |