THIS is how you SHOULD Structure your Golang Applications!?

In this video, I talk about software design/software architecture patterns in Golang. I dive into whether you should even bother with architecture patterns for your services, and the importance of picking when it is right to use something like Hexagonal architecture, Clean architecture or Domain Driven Design.

I also talk about just structuring side projects, and why sometimes just throwing something together is all you need to do until you start running into problems.

So in short, this video should you decide how to structure your Go microservices/services/applications.

[dejanduh]

Example repo would be nice, since you dont see everything from a video