provisioning-backend VS mage

I wrote a makefile which installs tools into PROJDIR/bin which is also in the gitignore.

Extremely simple in go, you just implement what is called Doer interface (one method). Here is an example from one of my projects, it is a simple decorator with logger in this case. Then you just initialize the client with this instance, in my project it is slightly more complex because I also setup OpenTelemetry but you get the idea.

Authentication and authorization is typically just a middleware which is essentially a function. Recently I implemented a RBAC functionality into our microservice which does not use any big framework. On our platform we have a RBAC service we need to call via REST. As you can see the whole patch is small if you exclude the generated OpenAPI client.

We use DAO/DAL in our app and I ran into the same problem - DAO does not work well with transactions. We have our own WithTransaction function which is currently only used within one model and that works fine. But the problem appears when we want to do a transaction across several models - that needs to be done in the business (service) layer.

Our project does have extensive makefile broken down into individual files so it is more readable. As you can see, we have targets for database, code quality, modules, testing, client generation, OpenAPI etc. It also has a trivial help:

Here is our code: https://github.com/RHEnVision/provisioning-backend/tree/main/pkg/worker

Our solution is simply one Redis queue, jobs have "type" (string) and are marshalled via Gob (for type safety) and there is no return value from job or error. This makes things extremely easy. We keep statistics (metrics) of job queue size and "in flight" jobs. Here is our implementation, just for inspiration. I suggest to write this on your own: https://github.com/RHEnVision/provisioning-backend/tree/main/pkg/worker

mage being a build tool and climate being a CLI library, a direct comparison probably doesn't make much sense but their parsing (https://github.com/magefile/mage/blob/master/parse/parse.go) seems very similar to what I'm doing for metadata (param names / godocs / comments etc.).

mage

https://github.com/magefile/mage but I haven't tried it as am not a fun of make like tools.

I prefer https://github.com/magefile/mage

We now use mage to cross-compile release binaries as proposed by u/g00py3 in this Reddit discussion.

Try github.com/magefile/mage - it's written in Go and lets you write Go to run scripts rather than writing bash inside yaml ;)

Mage v1.13 was released as of yesterday. This included a few small fixes, and a big new feature - subdirectory support.

If you need build automation, use mage.