Timeline for Improving the design of state transitions in a business application: the case of cancellation
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2017 at 20:19 | comment | added | Vignesh.N |
actually I do have an order cancellation reason, in my real system the SetStatus method takes in the reason as well. The status itself is a object and not a simple enum, and I do believe in the abstraction layer you talk about, Do you mean to say it is better for a IUserService to talk to IOrderCancelService to cancel an order and not call 'order.Cancel' if Order had an cancel method ?
|
|
| Jun 5, 2017 at 21:41 | comment | added | TheCatWhisperer | An interesting and thoughtful description of the problem cross entity coordination. What I would like to added is, your description and naming convention of the cross entity class which handles order cancellation. | |
| Jun 5, 2017 at 21:31 | history | answered | John Wu | CC BY-SA 3.0 |