This topic provides an overview of tenants in the OceanBase Database, including their definition and role.
OceanBase Database adopts a single-cluster multi-tenant design, allowing a cluster to accommodate multiple independent tenants. Tenants serve as the units for resource allocation and lay the foundation for managing database objects and resources.
Tenants can be thought of as similar to the concept of "instances" in traditional databases. They are completely isolated from one another, ensuring data security by prohibiting cross-tenant data access and safeguarding a tenant's data assets from theft by other tenants. Additionally, tenants have exclusive access to their allocated resource quotas. Essentially, tenants act as containers for various database objects and resources such as CPU, memory, and I/O.
Tenants are categorized into system tenants and user tenants based on their responsibilities. The system tenant, known as the sys tenant, is an integral part of OceanBase Database and is built-in. User tenants correspond to a typical database management system and can be viewed as a database instance created to meet the specific business needs of the sys tenant.
Furthermore, tenants are further classified into MySQL tenants and Oracle tenants based on their compatibility mode. Each type of tenant has its own syntax and functionality. In OceanBase Database, the sys tenant falls under the MySQL tenant category.
More information
For more information about tenants in OceanBase Database, see the following topics: