I just released Nexus Core v1.7.0 — moving from MongoDB to a database-agnostic architecture
I've just released Nexus Core v1.7.0, and this release is mainly about moving the persistence layer away from being tightly coupled to MongoDB.
Nexus Core was originally designed around MongoDB.
With v1.7.0, I introduced a generic database provider/driver abstraction and added support for:
- MongoDB
- PostgreSQL
- MySQL
The important change is that the core persistence layer is no longer directly tied to MongoDB-specific implementation details.
The architecture is now roughly:
Addons
↓
Nexus Core
↓
Database Provider
├── MongoDB
├── PostgreSQL
└── MySQL
The selected database provider is configured at the Nexus Core level, and the addons use that configured database backend.
So currently, a Nexus Core instance uses one selected database backend for its addons, rather than allowing each addon to use a completely different database.
The goal of this release was to create a clean abstraction that makes it possible to support different database engines without rewriting the persistence layer for every new backend.
There are also integration tests for the supported database adapters covering connection lifecycle, CRUD operations and protocol compatibility.
There is a breaking change for addons that directly depend on MongoDB-specific APIs. Those addons need to migrate to the new provider abstraction if they want to work with PostgreSQL or MySQL.
I'm particularly interested in feedback on the architecture itself.
If you've designed a database abstraction layer before:
Would you structure the provider/driver layer differently?
I'm especially interested in opinions about adapter boundaries, database-specific behavior and how you would design this if multi-database-per-instance support were added in the future.
Links
GitHub Repository:
https://github.com/mustafabinguldev/nexus-cache-orchestrator
Documentation:
https://nexus-core.mintlify.site/
v1.7.0 Changelog:
https://nexus-core.mintlify.site/reference/changelog#v1-7-0-—-multi-database-support-and-architecture-refactor-sep-11-2026
Feedback and architectural criticism are very welcome.
Posted Sep 11, 2026, 3:25 PM UTC