Hey Devs!, I wanted to share a side project I’ve been pouring time into lately: Goca.
If you’re like me, you’re tired of writing the same 20 files just to start a new Go service following Clean Architecture. The layers, the interfaces, the DI config—it’s necessary, but it’s pure boilerplate.
That’s where Goca comes in. It’s a CLI tool that generates a full, production-ready Go feature (entity, use case, repository, HTTP handler) in seconds, all while strictly enforcing Uncle Bob’s Clean Architecture rules. It’s essentially my way of cutting out the setup tax.
Heads up: This is still very much in beta. It’s working great for my own projects, but there are definitely rough edges, and I’m still figuring out the best ways to handle database migrations and multi-protocol setups.
It’s open source (MIT licensed), and I’m genuinely looking for feedback from people who actually build production Go apps. If you hate boilerplate as much as I do, please check out the documentation and let me know where it breaks for you.
Link to the docs:https://sazardev.github.io/goca/
Top comments (0)