gRPC Microservice Structure in Go! (DDD and Hexagonal Architecture Example)

Open source Github repo: github.com/sam...
In this video, I show an opinionated example of how you may structure a gRPC microservice in Golang. I discuss the advantages such from hexagonal architecture such as application layers, read and write repositories and the benefits of keeping your application logic outside of your transport layers.
The video does not showcase production-ready code but should give you a good idea of an approach you could take when implementing a microservice in Golang.
I took a lot of inspiration from the following repository github.com/pol... from ‪@polyscone‬ when implementing this example microservice - check the repository!
Twitter: / samvcodes
Github: github.com/sam...

[@dandogamer]

Would love to see a video on how you handle transactions within DDD, specifically handling the errors like rollbacks

[@paymonsattar222]

Wow sam, this is amazing!

[@samvcodes]

Ayy thanks Paymon!

[@prashlovessamosa]

Hey Sam can you please teach us event driven architecture and its implementation in Golang.

[@morkhoudia9]

Thanks you for this video

[@prashlovessamosa]

Bruv 5 months no upload

[@samvcodes]

Videos coming soon! Do you have any suggestions?

[@yassinenassih3002]

Thanks Man

[@samvcodes]

Thanks for watching! 🙏

[@anhhaoam3379]

Can you make a video about using sqlc in any project? and how to divide it into parts in repository , thanks ad

[@b3owu1f]

I like the project layout, but I always seem to have issues with using internal/ and getting other parts of the app to use it. Its great to hide anything not part of an API.. but when it's just an app for internal use other than "good practices" I dont' quite see the significance of the directory. It seems more relevant for projects that are libraries/sdks to be imported/used by other projects.

[@anshkumargarhewal8582]

Which theme are you using

[@TheMrlewismedia]

🙌🙏

[@samvcodes]

Thanks man!

[@lucifer-5ybtn]

programming font name?

[@ibrahimkoz1983]

You should define interfaces in the callsites that call for them. That is, you should not define your interfaces upfront as you did with your Reader and Writer interfaces.

[@jbarnett7045]

'promo sm'