OceanBase AI Database adopts a multi-tenant architecture. The multi-tenant architecture applies to scenarios such as resource consolidation and SaaS services and simplifies O&M.
A cluster is a physical concept in the deployment layer and is a collection of zones and nodes. Zones and nodes have attributes such as region. A tenant is a logical concept in the resource layer and is a resource unit defined on a physical node. You can specify the specifications of a resource unit, such as the CPU, memory, log disk space, and input/output operations per second (IOPS).
A tenant is similar to a database instance in a conventional database. A tenant is associated with resources by using a resource pool and thereby exclusively occupies a resource quota. The resource quota can be dynamically adjusted. You can create database objects such as databases, tables, and users in a tenant.
The concepts of resource specifications, resource units, and resource pools are the basis for understanding the concept of tenant. You can query the DBA_OB_UNIT_CONFIGS view for resource specifications, the DBA_OB_RESOURCE_POOLS view for resource pools, the DBA_OB_UNITS view for resource units, and the DBA_OB_TENANTS view for tenants.
Resource specifications
Resource specifications define the sizes of general physical resource items, such as the CPU, memory, disk space, and IOPS. When you create a resource pool, you must specify its resource specifications and then create resource units based on the specifications.
Resource unit (Unit)
The Unit is a very important concept in tenant management. OceanBase manages physical resources based on Units. A Unit is a collection of physical resources such as the CPU, memory, disk space, and IOPS. A Unit is also the basic unit for resource scheduling. It has location attributes such as node, zone, and region. A node is the abstraction of a server, a zone is the abstraction of an IDC, and a region is the abstraction of a geographic area. You can adjust the deployment mode of a tenant by adjusting the location attributes of its Units.
Resource pool
Each Unit belongs to a resource pool. A resource pool consists of multiple Units. A resource pool is the basic unit in resource allocation. All Units in the same resource pool have the same resource specifications. In other words, the sizes of physical resources are the same for all Units in the resource pool.

The preceding figure shows a resource pool named
a_poolthat consists of four Units. The resource pool has the following attributes:ZONE_LIST: Indicates the distribution of Units in zones, which isZONE_LIST='zone1,zone2'in this example.Unit_NUM: Indicates the number of Units in each zone specified byZONE_LIST, which is 2 in this example.Unit_CONFIG_ID: Indicates the ID of the resource specifications associated with the resource pool. The resource specifications define the sizes of physical resources in each Unit, such as the CPU, memory, log disk space, and IOPS.
The physical and logical concepts are associated based on Units in OceanBase AI Database. Each tenant has multiple Units distributed on multiple nodes in multiple zones. The Units on each node belong to different tenants. In short, a cluster consists of nodes and a node is the container of Units. A tenant consists of Units and a Unit is the container of database objects.
When you create a tenant, you can set RESOURCE_POOL_LIST to specify the resource pools associated with the tenant. The Units in these resource pools are intended for this tenant. For example, set RESOURCE_POOL_LIST to 'a_pool' for tenant a. The following figure shows the deployment.

This tenant is deployed across two zones and each zone has two Units. You can modify the Unit_CONFIG_ID parameter for the a_pool resource pool to dynamically adjust the physical resources for this tenant.
You can also modify the distribution of Units on different nodes in the same zone, which is called Unit migration, to achieve load balancing among the nodes. When a node fails, you can migrate the Units on it to other nodes in the same zone to implement automatic disaster recovery. You can modify the distribution of Units in different zones, namely, modify the locality of the tenant, to adjust the deployment mode of the tenant, thereby achieving different disaster recovery levels. General deployment modes include three IDCs in the same city, three IDCs across two regions, and five IDCs across three regions.