Master Vs Tenant Database

In our company’s ERP (Enterprise Resource Planning) solutions, we adopt a master-tenant database structure to efficiently manage data for multiple customers or organizations. This architecture allows us to maintain a single master database while accommodating separate tenant databases for each customer. In this section, we’ll explore the key concepts and benefits of the master-tenant database structure.

Understanding the Master-Tenant Architecture

• Master Database:
  The master database serves as the core database that contains shared resources and configurations. It typically stores system-level data, common functionalities, and configurations that are applicable to all tenants. This includes user management, global settings, and application-level features.

• Tenant Databases:
  Each tenant has its dedicated database, often referred to as a "tenant database" or "customer database." These databases are isolated from each other, ensuring data privacy and security for each customer. Tenant databases store customer-specific data, such as transactions, records, and configurations unique to that organization.

Throughout the documentation, you might encounter terms like master (sometimes "root") database and tenant database, and this is what they refer to. Each environment, like development, staging, and production, has one master database and multiple tenant databases connected to that master database.

Open

Figure: Multi-tenant Architecture