I like functions, especially higher-order ones and I think we often underestimate their power when working with Go. More often than not, we jump to creating a type and attaching a method to it when maybe a simple regular or higher-order function would do (standard library surely, makes use of this eg. http.HandlerFunc). I employ this approach often and I figured it wouldn’t hurt to share it. Where does this come from?...
Not long ago I have slowly started preparing material for a pragmatic hands-on book I’ve always wanted to write on the topic of event sourcing, where I would explore it in my own approachable way, applicable to any skill level while also spicing it up with golang, ports and adapters, tdd, testing, event driven architecture and good software engineering practices in general. It’s still early days and I am still fleshing it out....
Hexagonal / Ports and Adapters architecture in insert your language here How many of these have you seen before? Probably too many, but I promise, this will be a short one… Why another article? First, I have a confession to make. I have had this article in my backlog for at least four years now but have never “gotten around” to finishing it due to numerous reasons (the biggest one me simply being lazy)....