FeatureFuel
20

Multi-Database Support in Directus

Source: directus/directus#24545 · opened by @akefnetwork
Summary Enhancing Directus with multi-database support and separating system metadata from application data would significantly boost scalability, security, and overall flexibility. It would enable a single instance to manage multiple apps, each with distinct data requirements, while reducing overhead and complexity. Moreover, adding the ability to query multiple databases through the same API—like Hasura’s remote joins—would empower teams to unify data from various sources in one place. This improves developer productivity, fosters more advanced use-cases (analytics, microservices, etc.), and strengthens Directus’s appeal as a highly capable, all-in-one backend solution. Basic Example Motivation Currently, Directus only supports a single database per instance, limiting its ability to handle multi-tenant or multi-application environments. A forked version should: • Require two databases by default: - System Database (directus_system) → Stores system metada…

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests