liveBook · Manning

Driven adapter

As explained in Microservices Patterns, Second Edition

An adapter that enables application business logic to access external systems or services.

A driven adapter lets business logic make requests to external systems. In hexagonal architecture, it implements an outbound port, keeping the business logic independent of the adapter. section 3.3.2

A driven adapter can:

  • Access a database through a data access object implementing a repository-like port. section 3.3.2
  • Invoke a remote service through a proxy or publish events. section 3.3.2

FTGO integrations

FTGO uses outbound adapters to access its MySQL database and invoke cloud services such as Twilio and Stripe. section 2.1.1

Figure 3.16 An example of a hexagonal architecture, which consists of the business logic and one or more adapters that communicate with external systems. The business logic has one or more ports. Inbound adapters, which handles requests from external systems, invoke an inbound port. An outbound adapter implements an outbound port and invokes an external system.
Hexagonal architecture

The diagram shows business logic, outbound ports, and adapters invoking external systems. section 3.3.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the adapter’s port relationship and gives database, remote-service, and event examples.
Examples
Uses database access objects, remote-service proxies, event publication, and FTGO’s MySQL, Twilio, and Stripe integrations.
What you can do after
Understand how business logic requests external systems through outbound ports and adapters.
How it connects
Links outbound adapters to hexagonal architecture, ports, business logic, and data access objects.

Also explained in

Compare how 3 books explain driven adapter →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.