When integration direction is unclear, adapter responsibilities can get muddled. A driving actor is the external side that starts an inbound interaction: it calls an input adapter, which turns the request into a command or query and invokes a use case. The role belongs to the interaction, not permanently to the external system; the same system can be driven in an outbound interaction. section 10.1 section 10.7
Partner CMS
When a partner CMS asks to reopen an article, the CMS drives the use case; the domain decides whether reopening is allowed. section 10.1
Table 10.1 The same boundary, seen from each direction
|
Direction
|
Who starts
|
Adapter on the boundary
|
External system’s role
|
Example candidate
|
|
Inbound
|
The external system
|
Input adapter
|
Driving actor
|
A partner CMS asks to send an article back for review
|
|
Outbound
|
A WriteFlow use case
|
Output adapter
|
Driven actor
|
WriteFlow saves an article and tells the publishing platform about it
|
Compare who starts each interaction with the adapter and actor role at the boundary. section 10.1
