Driving adapter
A driving adapter receives input from an external actor or system, translates it into application terms, and invokes an application input port.
Clean Applications with Hexagonal Architecture
A primary adapter translates an external trigger into a call to an application input port.
- How it is used
- Separates external delivery mechanisms from the use cases they trigger in a hexagonal architecture.
- How deep it goes
- Defines adapter responsibilities and dependency direction, then gives implementation and controller-testing recipes.
- Examples
- Uses an article-publishing REST controller and message consumer to show different triggers reaching the same use case.
- What you can do after
- Builds a driving adapter that translates requests and results, dispatches commands or queries, and can be tested with mocked collaborators.
Read how Clean Applications with Hexagonal Architecture explains driving adapter →
Grokking Software Architecture
A hexagonal-architecture adapter that receives requests from outside the application, converts them into the core's terms, and calls a primary port.
- How it is used
- Routes requests from users, tests, or external systems into application logic through a primary port.
- How deep it goes
- Defines request translation and port handoff with controller examples; defers detailed REST, GraphQL, and API design.
- Examples
- Uses an OrderController handling JSON, plus web, mobile, test, CLI, and background-job entry points.
- What you can do after
- Apply the pattern by translating external requests into core terms and handing them to a primary port.
Read how Grokking Software Architecture explains driving adapter →
What to know first
- business logicBusiness logic is the domain-specific rules, computations, and decisions that determine how a software system processes operations and behaves.
- HTTP requestAn HTTP request is a message sent by a client to a server using the Hypertext Transfer Protocol, specifying a method and target and optionally including headers and a body.
Related concepts
- anticorruption layercontrasts with · An anticorruption layer is an integration boundary that translates between an external system’s model and an internal domain model, insulating the latter from unwanted external concepts and coupling.
- REST controllerincludes · A REST controller is a web component that handles HTTP requests for REST endpoints and dispatches them to application operations.
- sink nodeincludes · A sink node is a destination component or endpoint that receives data, messages, events, or flow from an upstream source for consumption or processing.
- use caseuses · A use case is a goal-oriented interaction or application scenario that describes how a system is expected to support an actor or practical objective.
- adapterkind of · An adapter is a software component that translates between interfaces or representations so otherwise incompatible components can work together.
Questions about driving adapter
What is driving adapter?
A driving adapter receives input from an external actor or system, translates it into application terms, and invokes an application input port.
Which Manning books explain driving adapter?
Clean Applications with Hexagonal Architecture and Grokking Software Architecture.
What should I know before learning driving adapter?
Manning books that teach driving adapter usually introduce business logic and HTTP request first.
What is the difference between driving adapter and anticorruption layer?
A driving adapter receives input from an external actor or system, translates it into application terms, and invokes an application input port. An anticorruption layer is an integration boundary that translates between an external system’s model and an internal domain model, insulating the latter from unwanted external concepts and coupling.
What kinds of driving adapter are there?
Kinds of driving adapter include REST controller and sink node.
What is driving adapter a kind of?
Driving adapter is a kind of adapter. An adapter is a software component that translates between interfaces or representations so otherwise incompatible components can work together.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

