Clarification on Multi-Database Support for Microservices Architecture
🔢DB Connections🟢SQL
I'm building a microservices platform and need guidance on the recommended approach for database isolation between services.
My Architecture:
- 3 microservices requiring separate databases:
What I Tried:
I executed CREATE DATABASE notification_db; in the SQL Editor. The command succeeded, but:
- The new database doesn't appear in the Supabase Dashboard
- We're unsure if connection pooling (Supavisor) works with additional databases
- Unclear if Supabase features (Auth, RLS) extend to these databases
My Questions:
1. Does Supabase officially support multiple databases within a single project?
2. If not, what's the recommended approach for service isolation?
- Schema-based isolation within one database?
- Separate Supabase projects per service?
3. If we use schemas, do all Supabase features (pooling, Auth, RLS) work correctly?
Environment:
- Planning for both staging and production environments
- Currently evaluating project structure before full setup
My Architecture:
- 3 microservices requiring separate databases:
What I Tried:
I executed CREATE DATABASE notification_db; in the SQL Editor. The command succeeded, but:
- The new database doesn't appear in the Supabase Dashboard
- We're unsure if connection pooling (Supavisor) works with additional databases
- Unclear if Supabase features (Auth, RLS) extend to these databases
My Questions:
1. Does Supabase officially support multiple databases within a single project?
2. If not, what's the recommended approach for service isolation?
- Schema-based isolation within one database?
- Separate Supabase projects per service?
3. If we use schemas, do all Supabase features (pooling, Auth, RLS) work correctly?
Environment:
- Planning for both staging and production environments
- Currently evaluating project structure before full setup
