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.
Comments
Similar requests
Get all related collections/items for m2o,m2m without reverse fields
2 votes · 0 comments
Activity Feed Presets and Bookmarks Missing
1 vote · 0 comments
Directus Loader for Astro Content Layer
41 votes · 0 comments
Ability to login to directus using access token of a configured provider.
2 votes · 0 comments
Why Isn't Directus Gaining More Attention in Mobile App Development?
10 votes · 0 comments
No comments yet.