liveBook · Manning

Driver actor

As explained in Clean Applications with Hexagonal Architecture

An external system or user that initiates an interaction by calling into an application.

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

How Clean Applications with Hexagonal Architecture covers it

How deep it goes
Defines the role through inbound direction and input-adapter flow, contrasting it with outbound driven actors.
Examples
Uses a partner CMS requesting article reopening, and identifies user interfaces and scheduled jobs as other examples.
What you can do after
Evaluate an integration by identifying who starts the interaction and which adapter belongs at the boundary.
How it connects
Connects driving actors to inbound integration, input adapters, use cases, and driven actors.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Clean Applications with Hexagonal Architecture. The section links point to the parts of the book it draws on.