ApsaraDB for OceanBase (Deprecated):Overview

Limitations

At present, you can enable the proxy service only for a cluster instance rather than a tenant instance.

Background

An ODP resides between the client and the database to receive requests from the client and forward the requests to OceanBase Database. To ensure optimal routing, ODP avoids distributed transactions. This ensures that the failure of a single server does not affect your business in multi-replica scenarios, improving the high availability of OceanBase Database.

The ODP cluster architecture V2.0 has been available since December 17, 2025. While ensuring high performance and high availability as V1.0, the new version provides more flexible scaling capabilities and allows you to create a separate proxy cluster for a specific endpoint by adding or removing nodes, implementing more fine-grained cluster specification control. For more information, see Manage the database proxy service.

Proxy types

OceanBase Database provides two specification types for the proxy service: general and exclusive.

• General: Your database proxy service instance shares CPU resources with other users. The specification of your database proxy service instance is allocated based on the actual size of your cluster. This specification type applies to business with stable and average traffic.

• Exclusive: Your database proxy service instance uses exclusive CPU resources. You can scale out the resource specification of your database proxy service instance based on business needs. This specification type applies to business with high access traffic. The proxy service of the exclusive specification type is charged based on the resource usage by hour.

The following table compares the two specification types.