We have created 4 library in golang with unique concept.
Please check below detail url:
https://github.com/Mindinventory?language=go
For further actions, you may consider blocking this person and/or reporting abuse
Read next
🚀 Go-ing Full-Stack: Building Dynamic Web Apps with Go 🐹, PostgreSQL 🐘, Docker 🐳, and HTTP Servers 🌐
Allan Githaiga -
How to Consistently Retrieve Valid JSON from Claude 3.5 in Go
Martin Beierling-Mutz -
Testing REST APIs in Go: A Guide to Unit and Integration Testing with Go's Standard Testing Library
sean -
Let's build a password generator we can actually use
IamKhan -
Top comments (2)
Great job.
Golang Project structure is especially interesting to me, as my code structure/layout of choice is still not settled.
Could you explain how you get to this structure?
And the benefits you see compared to others (Standard Project Layout, DDD, hex arch...)
I'm not willing to compare, but rather understand how you get there.
(to help me in my own process)
For example, my guidelines for a good architecture are simplicity, ease of testing, low duplication, loose coupling, easy substitution (should be easy to change logging, database...)
I have created my own structure.
I have used gorm framework but I did some customization in this boilerPlate.
Used group router, middleware, resources, ORM
If you like this then pls give me star on github.
github.com/Mindinventory?language=go