I’ve just released ZATRANO Framework 1.2, with a major improvement to database support.
ZATRANO is a Go framework focused on building modular monoliths and business applications, and database flexibility was one of the areas I wanted to improve.
With v1.2, multiple database engines are now a first-class feature:
-
SQLite
-
MySQL
-
PostgreSQL
-
SQL Server (MSSQL)
-
Oracle
-
MongoDB
Database configuration can be managed through DB_CONNECTIONS, while models can select their connection independently.
For example:
// SQL
app.DB().Connection("pgsql")
// MongoDB
container key: "mongo"
Database setup is also simplified with:
go run ./cmd/zatrano db:setup
The goal is to make it possible to build applications where different modules or models can use different database engines without introducing unnecessary complexity into the application architecture.
ZATRANO is still evolving, and I’m particularly interested in feedback from Go developers who build enterprise applications or modular monoliths.
What do you think about this approach to multi-database support in a Go framework?