Hexagonal architecture (software): Difference between revisions

Content deleted Content added

Revision as of 17:27, 23 October 2024 edit Asankama (talk \| contribs) 36 edits →See also Tag: Reverted ← Previous edit		Latest revision as of 17:53, 30 July 2025 edit undo The Anome (talk \| contribs) Edit filter managers, Administrators 260,142 edits →Principle: lowercase 'w' these days Tag: Visual edit
(One intermediate revision by one other user not shown)
Line 11: The hexagonal architecture divides a system into several loosely-coupled interchangeable components, such as the application core, the database, the user interface, test scripts and interfaces with other systems. This approach is an alternative to the traditional layered architecture. 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 [[Application programming interface\|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~~web service]]s). The granularity of the ports and their number is not constrained: Line 37: == See also == * [[Architectural pattern\|Architecture patterns]] * [[Cell-based architecture]] * [[Layer (object-oriented design)]] * [[Composite structure diagram]]