Zuul VS goa

Zuul (https://zuul-ci.org ) is specifically built for this use case. It was originally designed for OpenStack's CI, with OpenStack being broken down in multiple inter-dependent repos. Source: 5 months ago

If you’re already using gerrit I would strongly recommend looking at Zuul https://zuul-ci.org. Source: 10 months ago

Zuul (code) helps your team stop merging broken code -- the best kind of gatekeeping. - Source: dev.to / about 1 year ago

I wanted to share a package that I have created, and use, to interface the Zuul CI from Emacs. It offers completion for builds or buildsets, and implements a zuul-log-mode to browse the remote logs. Source: almost 2 years ago

Yay, yet another proprietary Zuul clone! 😶. Source: almost 2 years ago

My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / 5 days ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: 5 months ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: 10 months ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / 11 months ago

One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use... Source: 11 months ago