I'm building out a new REST API. It's purpose is to serve data to various clients. I'm trying to keep it generic so that it can be reused regardless of application as much as possible and trying to abstract out the Entity logic and Interactor logic out somehow and keep that decoupled from the basic Data API I'm building here.
With that I've been looking at Uncle Bob's Episode 7 video as well as brushing up on Hexagonal architecture (ports and adapters).
Question: Is a Hexagonal Architecture related in any way to Clean Architecture? In other words, in a Hexogonal Architecture, we have ports and adapters and then inside the hexagon, the application architecture. In Clean Architecture, we have Boundary Objects, Interactor Objects, Entity Objects (and probably lower level Repository Objects that talk to Data Layer CRUD objects). So do they cross paths? Such as I guess Clean Architecture in a Hexagonal model would be the application logic? Or maybe not? Do these two styles even cross paths or relate to each other at all? Do ports and adapters equate to Clean ARchitecture ideas such as boundary objects to any degree?