I've been taking some time recently to do an exploration of programming, by reading programming history and ideas about different paradigms and domains. I started focusing on how our abstractions get destroyed at the boundaries of programs.[0] I was surprised to discover a link between Hexagonal Architecture and functional programming.
Both try to drive towards a functional core. With HexArch, you'd need an imperative shell to interact with the world at the boundaries. With pure FP, the boundaries are manned by I/O monads and effects manager in the underlying runtime. [1][2]
Both try to drive towards a functional core. With HexArch, you'd need an imperative shell to interact with the world at the boundaries. With pure FP, the boundaries are manned by I/O monads and effects manager in the underlying runtime. [1][2]
[0] https://interjectedfuture.com/destroyed-at-the-boundary/
[1] https://www.destroyallsoftware.com/screencasts/catalog/funct....
[2] https://deque.blog/2017/07/06/hexagonal-architecture-a-less-...