Enable Multiple Mendix Apps to Share a Single PostgreSQL Database

Currently, each Mendix application requires its own database, even for test and staging environments. While this approach ensures isolation, it comes with significant cost implications for hosting, maintenance, and scalability. By enabling multiple Mendix apps to share a single PostgreSQL instance, especially in non-production environments, Mendix could help customers realize significant cost savings while streamlining database management.

Proposed Feature:

Extend Mendix’s database configuration options to support multi-tenancy at the application level within a single PostgreSQL database. Each Mendix app would have a dedicated schema or namespace within the shared database, ensuring data isolation without the need for entirely separate databases.

For environments where SQLite is supported (e.g., lightweight local deployments), a similar approach could enable local multi-app testing with minimal overhead.

Why This Matters:

1. Cost Optimization:

   • Eliminating the need for separate databases for every test or staging environment can drastically reduce hosting and operational costs.
   • This is particularly beneficial for organizations managing multiple Mendix apps, each requiring multiple environments.

2. Simplified Database Management:

   • Centralized management of a single database instance, with separate schemas for each app, reduces the administrative overhead.

3. Enhanced Flexibility:

   • Teams can spin up multiple environments quickly without worrying about database provisioning for each instance.

4. Aligned with Enterprise Needs:

   • Many enterprise systems already use PostgreSQL for multi-tenant scenarios. Leveraging this capability aligns Mendix closer to enterprise practices, fostering deeper adoption.

Implementation Considerations:

1. For PostgreSQL:

   • Use separate schemas or database roles to isolate app data within the same instance.
   • Build safeguards in Mendix Studio/Pro to prevent cross-app data conflicts or accidental data leakage.

2. For SQLite:

   • Allow Mendix apps to share a single SQLite file, with clear documentation on how apps are isolated using namespaces or prefixed tables.

3. Security & Compliance:

   • Ensure that access controls and encryption are robustly applied at the schema level to meet enterprise-grade security requirements.

Call to Action:

This feature would empower Mendix customers to save costs while maintaining flexibility and security, aligning with Mendix's vision of rapid and efficient application delivery. Let’s make Mendix even smarter, leaner, and more scalable—starting with smarter database use!

Vote for this idea if you believe Mendix should enable multi-app database sharing for better cost efficiency and operational excellence!