Hexagonal architecture (software): Difference between revisions

Revision as of 19:55, 12 August 2019

Revision as of 22:32, 12 August 2019

Line 12:

Each component is connected to the others through a number of exposed "ports". Communication through these ports follow a given protocol depending on their purpose. Ports and protocols define an abstract API that can be implemented by any suitable technical means (e.g. [[method invocation]] in an [[Object-oriented programming|object oriented language]], [[remote procedure call]]s, or [[Web service|web-services]]).

The granularity of the ports and theretheir number is not constrainted:

* a single port could in some case be sufficient (e.g. in the case of a simple service consumer) ;

* typically, there are ports for event sources (user interface, automatic feeding), notifications (outgoing notifications), [[database]] (in order to interface the component with any suitable DBMS), and administration (for controlling the component);