The invoke pattern coordinates an operation spanning domain modules through a direct method call. It is familiar and simple, and works well with transaction-per-operation. Its trade-off is design-time coupling: the risk of lock-step changes grows with the number of dependencies, especially when calls reach modules outside the caller’s core responsibilities. section 6.2.4
Creating an order
Order Management can call reserveCredit() on Consumer Management while creating an order. Calling Notification Management to send a confirmation email is a less suitable dependency because notifications are secondary to order management. section 6.2.4
Figure 6.16 The Invoke pattern is the most common and simplest collaboration mechanism. For example, the Order Domain Module can invoke the reserveCredit() method on the Consumer Management domain module.
Shows a direct call from Order Management to Consumer Management. section 6.2.4
