domain driven design - What does the choosing consistency type "Ask Whose Job It Is" guidance mean? -


Referring to how transactions or final compatibility should be used in Part II, it explains

While examining the case (or story) of use, ask whether the user is the task of executing the case to be processed or not, if so, then it corresponds to the transaction. Try to create, but overall the rules follow the same. If this is the work of another user, or the system's work, then allow it to eventually be compatible.

I do not follow. Is anyone a good example of implementing this rule of thumb?

How do I get it here:

  • Movable () on Chess Board gross => All responsibility should be taken in the responsibility of the user's responsibility within the ChessBoard limit.

  • DecideGameOver () on chess games gross => The responsibility of the system

    decides to subscribe to some handler Chessboard > PieceMoved event and representative for chess games , To decide whether the game ended. We can tolerate the delay between the last step taken on the board and when the game is updated grossly - this is the last compatibility.

    Although this is not a difficult and fast rule, more than a generalized general indicator with observation of dozens of systems.

Comments

Popular posts from this blog

ios - Adding an SKSpriteNode to SKScene from a child SKSpriteNode -

Matlab transpose a table vector -

c# - Textbox not clickable but editable -