Meet Joomiz, the thing I've been building in my free time
So, you are a developer and you need a database for a new service. You open a ticket. Someone from the platform team picks it up a few days later and creates the database by hand. If you work in a bigger company, maybe they run a pipeline instead. Then the password reaches you somehow: a chat message, an email, a file in a shared folder. Later you need the same thing for production, and the whole story starts again.
I've seen this in some companies. Not because the platform teams are slow, but because they do the same work again and again for every team that asks.
For the last months I've been working on a project to fix this. It's called Joomiz , and today I want to show you what it does.
One file, next to your code
The idea is simple. A feature team describes what a service needs in a file called joomiz.yaml , in the service's own repository. The platform team decides what can be in that file by configuring the Golden Path.…