flexible programming architecture diagram

#Flexible programming architecture diagram software

The center hexagon is the core of the application (the business and application logic). Imagine a hexagon shape with another, larger hexagon shape around it. Cockburn explains that the authors 'call stereotype 'Interfacers,' but show examples of them using the GoF pattern 'Adapter.'' It's important to note the use of the term 'Interfacers' in that wiki entry because that's really what it's all about! But the 'hexagonal architecture' name stuck, and that's the name many people know it by today.Ĭockburn had his 'eureka moment' about ports and adapters after reading Object Design: Roles, Responsibilities, and Collaborations by Rebecca Wirfs-Brock and Alan McKean. 'Hexagonal architecture' was actually the working name for the ' ports and adapters pattern,' which is the term Cockburn settled on in the end. Hexagonal architecture was proposed by Alistair Cockburn in 2005. Hexagonal Architecture? More Like Ports and Adapters! There's a bit of interesting trivia about its origins. And this was the primary motivation for the creation of hexagonal architecture in the first place. But there's a key difference in the hexagonal model: the UI can be swapped out, too. It's possible to use dependency injection and other techniques in layered architecture to enable testing. Hexagonal architecture was a departure from layered architecture. You can swap in fakes for testing, which makes the tests more stable. One major appeal of using hexagonal architecture is that it makes your code easier to test. Having inputs and outputs at the edge means you can swap out their handlers without changing the core code. In doing so, you isolate the central logic (the core) of your application from outside concerns. The idea behind it is to put inputs and outputs at the edges of your design.

#Flexible programming architecture diagram software

Hexagonal architecture is a model or pattern for designing software applications.