This topic provides the definitions of terms that you may need to know when you use OAT.
OAT: OceanBase Administrator Tool, which is used to install and manage OceanBase ecosystem products and components.
OceanBase Database: A distributed relational database that supports MySQL and Oracle modes.
Ecosystem products: OceanBase ecosystem products, including OceanBase Cloud Platform (OCP), OceanBase Developer Center (ODC), OceanBase Access Proxy (OB Sharding), and OceanBase Migration Service (OMS).
- OCP: OceanBase Cloud Platform, which is used to manage OceanBase clusters.
- ODC: OceanBase Developer Center, which is used for database development.
- OMS: OceanBase Migration Service, which is used for data interaction between homogeneous or heterogeneous data sources and OceanBase Database.
- OB Sharding: An OceanBase Database-specific proxy service that receives SQL requests from users, forwards the SQL requests to the best target server, and returns the execution results to users.
Components: OceanBase components, including MetaDB, OBDNS, and InfluxDB.
- MetaDB: A container-based OceanBase Database service that is pre-installed with OceanBase Proxy for direct external access. It can store metadata for OCP, ODC, and OMS.
- OBDNS: A container-based DNS + Tengine load balancing service. If you do not have an external load balancing device (such as F5), you can use it as a soft load balancer. However, you must configure the DNS server to the server where OBDNS is deployed. It can provide load balancing and high availability for OCP and other ecosystem products.
- InfluxDB: A container-based time series database service that stores the monitoring data of data transmission links in OMS.
- NLB: A load balancer based on OpenResty. It has the advantages of high availability, simple deployment, and low resource consumption. It can provide load balancing for OCP, ODC, and OMS.
- OpenSearch: A distributed search and analysis engine based on Lucene. It supports real-time data storage, retrieval, and complex analysis. It has high scalability and can easily build clusters to handle massive data. It provides flexible queries through RESTful APIs. It is widely used in log analysis, full-text search, and real-time data monitoring. It can quickly process structured and unstructured data, helping enterprises gain insights and optimize decisions. OCP uses OpenSearch to retain logs for end-to-end tracing. O&M engineers can view the execution time of each transaction or each SQL statement in the entire chain of access on OCP, thereby identifying issues in the entire access chain.
Tools: Peripheral O&M tools that can be selected upon delivery. Currently, only OBLB is available.
- OBLB: A load balancing service based on iptables. If you do not have an external load balancing device (such as F5) and the traffic is not heavy, you can use it as a soft load balancer for OceanBase clusters.