- Mycel is a zero code microservice runtime that turns plain config files into working REST APIs with full CRUD support.
- A complete zero code microservice backed by SQLite needs just three files and a single Docker command to run.
- Mycel handles HTTP routing, query execution, JSON marshalling, and validation automatically — no application code required.
- Built-in Prometheus metrics, health checks, and a debug endpoint come free with every Mycel service, declared or not.
- Mycel is a zero code microservice runtime that turns plain config files into working REST APIs with full CRUD support.
- A complete zero code microservice backed by SQLite needs just three files and a single Docker command to run.
- Mycel handles HTTP routing, query execution, JSON marshalling, and validation automatically — no application code required.
- Built-in Prometheus metrics, health checks, and a debug endpoint come free with every Mycel service, declared or not.
The Plumbing Problem Nobody Talks About Honestly
Every zero code microservice pitch starts with the same uncomfortable truth: most microservice code is boring. Not intellectually demanding, not architecturally interesting — just repetitive plumbing that every developer rewrites from scratch on every new project. A new router. A new handler. A DTO. A validation layer. A database pool. Query logic. JSON marshalling. Error handling wrapped around all of it. Then you start the next service and do it all over again with different variable names.
That’s the reality a developer named Matute Tandil decided to push back against with Mycel, an open-source runtime that replaces application code with configuration. The pitch is stark: describe the shape of your service — which endpoint reads from which database table — and Mycel handles the execution. Same binary, every service, only the config changes.
It’s the nginx mental model applied to microservices. You don’t write the socket loop to run nginx; you write a config file and let the binary handle the rest. Mycel asks why we haven’t done the same thing for the layer above the network.
What a Zero Code Microservice Actually Looks Like
The structure is deliberately minimal. A working CRUD API backed by SQLite uses exactly three configuration files. The first defines the service identity — name, version. The second declares connectors: one for the HTTP server, one for the database. The third wires them together using flows.
A connector in Mycel is a bidirectional adapter. It can be a data source, a data target, or both. An HTTP REST connector listens for incoming requests. A database connector speaks to SQLite, PostgreSQL, or whatever driver you’ve configured. A flow is the binding between them — it says
