{"id":76,"date":"2026-04-12T18:04:16","date_gmt":"2026-04-12T18:04:16","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-apsaradb-for-oceanbase-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-databases\/"},"modified":"2026-04-12T18:04:16","modified_gmt":"2026-04-12T18:04:16","slug":"alibaba-cloud-apsaradb-for-oceanbase-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-databases","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-apsaradb-for-oceanbase-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-databases\/","title":{"rendered":"Alibaba Cloud ApsaraDB for OceanBase Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Databases"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Databases<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>ApsaraDB for OceanBase is Alibaba Cloud\u2019s fully managed service for the OceanBase distributed relational database. It is designed for applications that need high availability, horizontal scalability, and strong consistency without running and operating a complex distributed database platform yourself.<\/p>\n\n\n\n<p>In simple terms: <strong>you create an OceanBase database instance in Alibaba Cloud, connect to it using standard SQL clients, and let the managed service handle core operations<\/strong> such as provisioning, patching (where supported), backups, monitoring, and high availability configurations.<\/p>\n\n\n\n<p>Technically, ApsaraDB for OceanBase provides a managed control plane around the OceanBase database engine (a distributed, strongly consistent relational database). OceanBase commonly supports <strong>MySQL-compatible mode<\/strong> and <strong>Oracle-compatible mode<\/strong> (confirm exact compatibility and supported versions in the official docs for your region\/edition). It uses a distributed architecture with replicas across zones and a proxy layer for routing connections.<\/p>\n\n\n\n<p>The problem it solves: <strong>running business-critical relational workloads at scale<\/strong> (often multi-terabyte to petabyte scale and high QPS\/transactions) while reducing the operational burden and risk of self-managing a distributed database cluster.<\/p>\n\n\n\n<blockquote>\n<p>Service naming note: As of the latest publicly available Alibaba Cloud materials, the managed service is marketed as <strong>ApsaraDB for OceanBase<\/strong> on Alibaba Cloud. If you see \u201cOceanBase Database\u201d used elsewhere, it may refer to the database engine\/product family; always confirm the managed-service SKU and console workflow in the official docs for your account and region.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is ApsaraDB for OceanBase?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose<\/h3>\n\n\n\n<p>ApsaraDB for OceanBase is a <strong>managed distributed relational database service<\/strong> on Alibaba Cloud built on the OceanBase database engine. Its purpose is to provide a scalable, highly available relational database suitable for demanding OLTP workloads and enterprise migrations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities (high level)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Managed provisioning of OceanBase instances\/clusters in Alibaba Cloud<\/li>\n<li>High availability through multi-replica, multi-zone deployment options (availability depends on region and selected architecture)<\/li>\n<li>SQL access in <strong>MySQL-compatible<\/strong> and\/or <strong>Oracle-compatible<\/strong> modes (verify supported modes and feature parity)<\/li>\n<li>Tenant-based resource isolation (OceanBase commonly uses \u201ctenants\u201d as isolation boundaries inside a cluster)<\/li>\n<li>Backup\/restore and operational visibility via Alibaba Cloud console tools<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components you will encounter<\/h3>\n\n\n\n<p>While the exact names in the console may vary by edition\/version, the common building blocks are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OceanBase cluster \/ instance<\/strong>: The distributed database deployment you purchase and operate.<\/li>\n<li><strong>Zones \/ replicas<\/strong>: OceanBase deployments typically place replicas across multiple zones for HA.<\/li>\n<li><strong>Tenants<\/strong>: Logical isolation units inside a cluster, often used to separate workloads, environments, or applications.<\/li>\n<li><strong>Proxy layer (commonly OceanBase Database Proxy \/ OBProxy \/ ODP)<\/strong>: A routing layer that provides a stable endpoint and routes SQL connections to the correct nodes\/partitions.<\/li>\n<li><strong>Management plane<\/strong>: The Alibaba Cloud console and supporting services for monitoring, backups, and lifecycle operations.<\/li>\n<\/ul>\n\n\n\n<blockquote>\n<p>Terminology varies across OceanBase documentation and Alibaba Cloud console pages. Treat the console terms as the source of truth for your environment and <strong>verify in official docs<\/strong> when mapping \u201cinstance\/cluster\/tenant\u201d concepts.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed database (DBaaS)<\/strong> on Alibaba Cloud, in the <strong>Databases<\/strong> category.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope (regional\/zonal\/account\/project)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Account-scoped<\/strong>: Resources belong to your Alibaba Cloud account.<\/li>\n<li><strong>Region-scoped<\/strong>: Instances are created in a specific Alibaba Cloud region.<\/li>\n<li><strong>Multi-zone capable<\/strong>: Many production deployments place replicas across multiple zones within a region for resilience. Cross-region options may exist (for DR) but should be verified for your SKU\/region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the Alibaba Cloud ecosystem<\/h3>\n\n\n\n<p>ApsaraDB for OceanBase typically integrates with:\n&#8211; <strong>VPC<\/strong> networking (private access patterns)\n&#8211; <strong>ECS<\/strong> for application hosts\/bastion hosts\n&#8211; <strong>CloudMonitor<\/strong> for metrics and alerting (verify OceanBase metric set and integration)\n&#8211; <strong>Log Service (SLS)<\/strong> for logs (availability depends on edition\/features)\n&#8211; <strong>KMS<\/strong> for encryption key management (where encryption options support KMS integration)\n&#8211; <strong>RAM<\/strong> for identity and access management to control who can administer the service<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use ApsaraDB for OceanBase?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reduced operational burden<\/strong> compared with self-managing a distributed database (provisioning, HA layout, backups, lifecycle operations).<\/li>\n<li><strong>Faster time-to-market<\/strong> for systems that need scale and reliability beyond a single-node database.<\/li>\n<li><strong>Migration path<\/strong> for enterprises with large relational estates (particularly MySQL\/Oracle-style SQL patterns), subject to compatibility verification.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Distributed architecture<\/strong> designed to scale horizontally.<\/li>\n<li><strong>Strong consistency<\/strong> and fault tolerance patterns (OceanBase is known for consensus-based replication; validate implementation details for your edition\/version).<\/li>\n<li><strong>Compatibility modes<\/strong> that can ease porting existing SQL and tools (verify exact compatibility limits).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Built-in lifecycle management and visibility in Alibaba Cloud console.<\/li>\n<li>Automated or guided backup\/restore workflows.<\/li>\n<li>Easier HA configuration than manual multi-node setups.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Private networking in VPC<\/li>\n<li>Fine-grained administrative access via Alibaba Cloud RAM<\/li>\n<li>Auditing and logging options (verify what\u2019s available in your region\/edition)<\/li>\n<li>Encryption options (at rest\/in transit) depending on configuration<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Designed for high-concurrency OLTP workloads.<\/li>\n<li>Multi-tenant resource isolation patterns (tenants + resource pools, depending on model).<\/li>\n<li>Ability to scale resources and distribute data\/compute across nodes (verify supported scale operations and constraints).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose it<\/h3>\n\n\n\n<p>Choose ApsaraDB for OceanBase when you need:\n&#8211; A managed, distributed relational database on Alibaba Cloud\n&#8211; HA across zones within a region\n&#8211; A path to run large OLTP workloads that outgrow single-node DB instances\n&#8211; MySQL\/Oracle-style SQL compatibility requirements (after testing)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Avoid or reconsider if:\n&#8211; You only need a small, single-node relational database (ApsaraDB RDS or a smaller managed DB may be simpler\/cheaper).\n&#8211; You need a database specialized for analytics\/OLAP at scale (consider Alibaba Cloud analytic services; OceanBase may not be the best fit for heavy analytics unless your edition explicitly supports the needed features).\n&#8211; Your application depends on niche MySQL\/Oracle behaviors that are not supported (compatibility is not always 100%).\n&#8211; You require a multi-cloud managed service with identical operational tooling everywhere.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is ApsaraDB for OceanBase used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Fintech and payments (transaction-heavy systems)<\/li>\n<li>E-commerce and retail (orders, inventory, carts)<\/li>\n<li>Logistics and supply chain (event-driven OLTP)<\/li>\n<li>Telecom and IoT platforms (device state, customer data)<\/li>\n<li>Gaming (player profiles, economies)<\/li>\n<li>Enterprise SaaS (multi-tenant OLTP)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Platform engineering teams standardizing a database platform<\/li>\n<li>SRE\/operations teams managing HA and incident response<\/li>\n<li>Application teams building transactional microservices<\/li>\n<li>Data engineering teams supporting mixed workloads (with careful design)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OLTP systems with high write concurrency<\/li>\n<li>Multi-tenant SaaS relational workloads<\/li>\n<li>Large-scale sharded-database consolidation (migrate from manual sharding to a distributed database)<\/li>\n<li>Cross-zone HA database backends for critical apps<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Microservices with per-service schemas<\/li>\n<li>Shared database with tenant isolation<\/li>\n<li>Event-driven apps needing transactional integrity<\/li>\n<li>Hybrid architectures combining relational OLTP + separate analytics stores<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Real-world deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Production: HA multi-zone cluster\/instance, private access in VPC, strict RAM controls, scheduled backups, alerting, runbooks.<\/li>\n<li>Dev\/test: smaller instances, fewer zones, shorter backup retention, cost controls and auto-stop patterns where applicable (verify availability).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios where ApsaraDB for OceanBase is commonly a good fit. For each, validate feature availability (modes, backups, DR, scaling) in your region\/edition.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Replace manual MySQL sharding<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Application has dozens\/hundreds of MySQL shards; operations and query complexity are growing.<\/li>\n<li><strong>Why this service fits:<\/strong> A distributed relational database can reduce shard sprawl and centralize operations.<\/li>\n<li><strong>Example:<\/strong> An e-commerce platform consolidates 128 MySQL shards into OceanBase and keeps application SQL mostly unchanged (after compatibility testing).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) High availability for a core payment ledger<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A single primary database is a single point of failure; RPO\/RTO requirements are strict.<\/li>\n<li><strong>Why this service fits:<\/strong> Multi-zone replica design and managed HA improve resilience.<\/li>\n<li><strong>Example:<\/strong> Payment ledger writes must remain strongly consistent during zone-level failures.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Multi-tenant SaaS with strict tenant isolation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need to isolate noisy neighbors and separate tenants for compliance.<\/li>\n<li><strong>Why this service fits:<\/strong> Tenant-based resource allocation and logical isolation.<\/li>\n<li><strong>Example:<\/strong> A SaaS platform places regulated customers into separate tenants with distinct resource allocations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Consolidate many small databases into fewer managed clusters<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Hundreds of small DBs increase admin overhead and cost.<\/li>\n<li><strong>Why this service fits:<\/strong> Consolidation via tenants\/schemas can reduce sprawl.<\/li>\n<li><strong>Example:<\/strong> A company merges many departmental MySQL instances into a smaller number of managed OceanBase deployments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Build a transactional backend for order processing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> High QPS order creation with strict consistency requirements.<\/li>\n<li><strong>Why this service fits:<\/strong> OLTP-focused distributed design.<\/li>\n<li><strong>Example:<\/strong> \u201cCreate order \u2192 reserve inventory \u2192 charge payment\u201d relies on durable transactions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Modernize legacy Oracle-style applications (compatibility mode)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Legacy app relies on Oracle SQL\/PLSQL patterns and tooling.<\/li>\n<li><strong>Why this service fits:<\/strong> Oracle-compatible mode may reduce refactoring (verify supported features).<\/li>\n<li><strong>Example:<\/strong> An enterprise migrates selected schemas and stored programs after a proof-of-concept compatibility assessment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Cross-zone resilient database for Kubernetes workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Kubernetes services scale across zones, but DB is single-zone.<\/li>\n<li><strong>Why this service fits:<\/strong> Multi-zone DB aligns with multi-zone app scheduling.<\/li>\n<li><strong>Example:<\/strong> ACK (Alibaba Cloud Kubernetes) workloads connect privately to OceanBase in the same VPC.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Build a financial reporting OLTP store with strong integrity constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> High integrity and transactional constraints with predictable performance.<\/li>\n<li><strong>Why this service fits:<\/strong> ACID transactions and distributed HA.<\/li>\n<li><strong>Example:<\/strong> Accounting entries and balances are stored with strict constraints and controlled access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Central user profile store with massive concurrency<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> User profile reads\/writes are hot and constantly changing.<\/li>\n<li><strong>Why this service fits:<\/strong> Horizontal scale and managed operations.<\/li>\n<li><strong>Example:<\/strong> A social app stores user settings, sessions, and preferences.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Hybrid cloud-to-Alibaba Cloud migration landing zone<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need a stable managed database as a landing zone during phased migration.<\/li>\n<li><strong>Why this service fits:<\/strong> Managed service reduces operational overhead during transition.<\/li>\n<li><strong>Example:<\/strong> Data replicates from on-prem into OceanBase while applications migrate in waves.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Reduce operational toil for HA and backup compliance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Self-managed DB requires constant patching, backups, and HA validation.<\/li>\n<li><strong>Why this service fits:<\/strong> Managed backups\/monitoring and standardized operational patterns.<\/li>\n<li><strong>Example:<\/strong> A small ops team runs business-critical DB with less manual work.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Large-scale catalog and inventory systems<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Catalog tables are large; writes are frequent; low latency matters.<\/li>\n<li><strong>Why this service fits:<\/strong> Distributed scale and controlled resource allocation.<\/li>\n<li><strong>Example:<\/strong> Global product catalog and inventory reservations with high concurrency.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<blockquote>\n<p>Exact feature names and availability can vary by region, engine version, and edition. Confirm in the official docs and console for your account.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Managed provisioning and lifecycle<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Create, resize, and manage OceanBase deployments through the Alibaba Cloud console.<\/li>\n<li><strong>Why it matters:<\/strong> Eliminates manual cluster setup, reduces risk.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster environment creation for dev\/test\/prod with repeatable configurations.<\/li>\n<li><strong>Caveats:<\/strong> Some operations can be disruptive or require maintenance windows; verify resizing behavior.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Distributed high availability (multi-zone replicas)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Maintains replicas across zones (commonly three replicas) to tolerate failures.<\/li>\n<li><strong>Why it matters:<\/strong> Improves availability and durability for critical workloads.<\/li>\n<li><strong>Practical benefit:<\/strong> Continued service during instance\/node\/zone failures depending on architecture.<\/li>\n<li><strong>Caveats:<\/strong> HA depends on correct zone selection, quorum, and network stability.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">MySQL-compatible mode \/ Oracle-compatible mode<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides SQL interfaces aligned with MySQL and\/or Oracle ecosystems.<\/li>\n<li><strong>Why it matters:<\/strong> Reduces migration effort and lets you reuse tools\/drivers.<\/li>\n<li><strong>Practical benefit:<\/strong> Many apps can connect using familiar client libraries.<\/li>\n<li><strong>Caveats:<\/strong> Compatibility is rarely perfect. Test critical SQL, data types, isolation semantics, and procedural features.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tenant-based isolation and resource governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Separates workloads using tenants and resource allocations (CPU\/memory) inside a cluster.<\/li>\n<li><strong>Why it matters:<\/strong> Prevents noisy neighbor issues and supports organizational separation.<\/li>\n<li><strong>Practical benefit:<\/strong> Run multiple environments\/apps while controlling performance isolation.<\/li>\n<li><strong>Caveats:<\/strong> Misconfigured resources can cause throttling; tenant sizing is a skill.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Backup and restore<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides backup policies and restore workflows (point-in-time restore may be available depending on edition).<\/li>\n<li><strong>Why it matters:<\/strong> Essential for disaster recovery and operational safety.<\/li>\n<li><strong>Practical benefit:<\/strong> Recover from accidental deletes, corruption, or application bugs.<\/li>\n<li><strong>Caveats:<\/strong> Backup retention and restore times affect costs and RTO; verify PITR support and limits.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring and alerting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Exposes key metrics (CPU\/memory usage, QPS\/TPS, latency, storage, connections) and supports alarms.<\/li>\n<li><strong>Why it matters:<\/strong> Enables proactive operations and SRE practices.<\/li>\n<li><strong>Practical benefit:<\/strong> Detect performance regressions, resource saturation, and abnormal error rates early.<\/li>\n<li><strong>Caveats:<\/strong> Metric granularity and retention may vary; integrate with CloudMonitor where supported.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network security with VPC and access control<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Runs in VPC and typically uses allowlists\/whitelists and security group rules to control access.<\/li>\n<li><strong>Why it matters:<\/strong> Reduces public exposure and enforces least privilege at the network layer.<\/li>\n<li><strong>Practical benefit:<\/strong> Private endpoints for apps inside the same VPC; controlled admin access.<\/li>\n<li><strong>Caveats:<\/strong> Misconfigured allowlists are a common connectivity issue.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Connection endpoint via proxy layer<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides a stable endpoint that routes connections to appropriate nodes.<\/li>\n<li><strong>Why it matters:<\/strong> Simplifies application connection management in a distributed system.<\/li>\n<li><strong>Practical benefit:<\/strong> Fewer changes needed during scaling\/failover.<\/li>\n<li><strong>Caveats:<\/strong> Proxy layer has its own capacity limits and operational considerations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational tooling (console workflows)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> UI-driven workflows for common tasks: create tenant, manage users, view performance, run diagnostics.<\/li>\n<li><strong>Why it matters:<\/strong> Makes day-2 operations approachable for teams new to OceanBase.<\/li>\n<li><strong>Practical benefit:<\/strong> Standardized runbooks and quicker troubleshooting.<\/li>\n<li><strong>Caveats:<\/strong> Some advanced tuning still requires deep database expertise.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level service architecture<\/h3>\n\n\n\n<p>ApsaraDB for OceanBase is typically deployed as:\n&#8211; An OceanBase <strong>database cluster<\/strong> spread across multiple <strong>zones<\/strong> within a <strong>region<\/strong>\n&#8211; A <strong>proxy endpoint<\/strong> that applications connect to\n&#8211; A managed <strong>control plane<\/strong> in Alibaba Cloud that handles provisioning, monitoring, backups, and lifecycle operations<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (conceptual)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Application (or admin client) connects to the OceanBase endpoint (often a proxy endpoint).<\/li>\n<li>Proxy routes the connection to the appropriate OceanBase nodes\/partitions.<\/li>\n<li>Writes are replicated to other replicas according to the system\u2019s consensus\/replication mechanism.<\/li>\n<li>Control-plane operations (scaling, backups, parameter changes) are issued via console\/API and executed against the database system with guardrails.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related Alibaba Cloud services (common patterns)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ECS<\/strong>: Bastion host or application hosts used to connect privately.<\/li>\n<li><strong>VPC \/ vSwitch \/ Security Groups<\/strong>: Primary network boundary.<\/li>\n<li><strong>CloudMonitor<\/strong>: Metrics and alerting (verify supported metrics).<\/li>\n<li><strong>Log Service (SLS)<\/strong>: Central log collection (verify available logs\/integration).<\/li>\n<li><strong>Object Storage Service (OSS)<\/strong>: Often used as backup storage behind the scenes (implementation details are managed; confirm data residency and configuration options).<\/li>\n<li><strong>RAM<\/strong>: Fine-grained access control to manage who can administer instances.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<p>At minimum, you should plan for:\n&#8211; A <strong>VPC<\/strong> and subnets (vSwitches)\n&#8211; Compute for clients\/admin access (ECS or on-prem connectivity)\n&#8211; Optional: CloudMonitor alarms, SLS, Bastion host<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Administrative access<\/strong>: Controlled by Alibaba Cloud <strong>RAM<\/strong> policies for console\/API actions (create instance, delete instance, view metrics).<\/li>\n<li><strong>Database access<\/strong>: Controlled by database users\/roles inside OceanBase (SQL GRANT\/REVOKE semantics depend on mode).<\/li>\n<li><strong>Network access<\/strong>: Controlled by VPC routing, security groups, and any OceanBase allowlist\/whitelist mechanisms in the console.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Typically <strong>private access within VPC<\/strong> is preferred for production.<\/li>\n<li>If public endpoints are offered, use them only with strict allowlisting and encryption in transit. Availability and configuration vary\u2014<strong>verify in official docs<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Establish baseline dashboards: CPU\/memory, storage, QPS\/TPS, latency, slow queries.<\/li>\n<li>Use alarm thresholds aligned with SLOs (not just resource usage).<\/li>\n<li>Tag resources (instances, ECS, VPC) consistently for cost allocation and incident response.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (conceptual)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  App[Application \/ SQL Client] --&gt;|JDBC\/ODBC\/MySQL protocol| Proxy[OceanBase Proxy Endpoint]\n  Proxy --&gt; OB1[OceanBase Node - Zone A]\n  Proxy --&gt; OB2[OceanBase Node - Zone B]\n  Proxy --&gt; OB3[OceanBase Node - Zone C]\n  OB1 &lt;--&gt;|Replication \/ Consensus| OB2\n  OB2 &lt;--&gt;|Replication \/ Consensus| OB3\n  OB3 &lt;--&gt;|Replication \/ Consensus| OB1\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style reference architecture (typical on Alibaba Cloud)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph VPC[VPC (Private Network)]\n    subgraph AppTier[Application Tier (Multi-AZ)]\n      SLB[Server Load Balancer]\n      ACK[ECS\/ACK Worker Nodes]\n      SLB --&gt; ACK\n    end\n\n    subgraph DBTier[ApsaraDB for OceanBase (Multi-Zone)]\n      ODP[OceanBase Proxy Endpoint]\n      OBZA[OceanBase Zone A Nodes]\n      OBZB[OceanBase Zone B Nodes]\n      OBZC[OceanBase Zone C Nodes]\n      ODP --&gt; OBZA\n      ODP --&gt; OBZB\n      ODP --&gt; OBZC\n      OBZA &lt;--&gt;|Replication| OBZB\n      OBZB &lt;--&gt;|Replication| OBZC\n      OBZC &lt;--&gt;|Replication| OBZA\n    end\n\n    ACK --&gt;|Private SQL| ODP\n\n    Bastion[ECS Bastion Host] --&gt;|Admin SQL| ODP\n  end\n\n  CloudMonitor[CloudMonitor Alarms] --&gt; DBTier\n  SLS[Log Service (SLS)] -.-&gt; DBTier\n  OSS[OSS (Backups, if applicable)] -.-&gt; DBTier\n  RAM[RAM (IAM)] --&gt; DBTier\n<\/code><\/pre>\n\n\n\n<blockquote>\n<p>The dashed integrations (SLS\/OSS) depend on your configuration and product edition. Confirm exact integration points and controls in the official documentation.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<p>Before starting the lab and planning a real deployment, ensure you have:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Account and billing<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An <strong>Alibaba Cloud account<\/strong> with billing enabled.<\/li>\n<li>Sufficient quota to create database instances in the chosen region.<\/li>\n<li>A payment method for <strong>Pay-as-you-go<\/strong> or <strong>Subscription<\/strong> (availability depends on the service offering in your region).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions (RAM)<\/h3>\n\n\n\n<p>You need RAM permissions to:\n&#8211; Create and delete ApsaraDB for OceanBase instances\n&#8211; View and manage VPC resources (VPC\/vSwitch\/security groups)\n&#8211; Create and manage ECS instances (for client connectivity in the lab)\n&#8211; View monitoring metrics and configure alarms (optional)<\/p>\n\n\n\n<p>If your organization uses least-privilege, ask your cloud admin for a policy that includes the minimum set of actions for:\n&#8211; OceanBase service management\n&#8211; ECS and VPC read\/write needed for the lab<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Tools<\/h3>\n\n\n\n<p>For the hands-on tutorial, you\u2019ll use:\n&#8211; Alibaba Cloud Console (browser)\n&#8211; An SQL client:\n  &#8211; <code>mysql<\/code> CLI for MySQL-compatible mode, or\n  &#8211; A GUI such as DBeaver\/DataGrip (optional)\n&#8211; An ECS instance (Linux) in the same VPC for private connectivity testing<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Choose a region where <strong>ApsaraDB for OceanBase<\/strong> is available.<\/li>\n<li>Some instance architectures (multi-zone, specific modes, DR) may be region-limited.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits (examples to verify)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Max instances per region\/account<\/li>\n<li>Max tenants per cluster\/instance<\/li>\n<li>Max connections per tenant<\/li>\n<li>Storage limits and backup retention maximums<\/li>\n<li>Network constraints (public endpoint availability, allowed CIDRs)<\/li>\n<\/ul>\n\n\n\n<blockquote>\n<p>Always check the <strong>Quotas<\/strong> and <strong>Limits<\/strong> section of the official docs for your region\/edition.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>VPC + vSwitch in the selected region<\/li>\n<li>ECS for testing connectivity (recommended)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<blockquote>\n<p>Do not treat this as a quote. Pricing for ApsaraDB for OceanBase varies by region, instance architecture, edition, and purchase model. Always confirm on the official pricing page for your region.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Official pricing sources<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Product page: https:\/\/www.alibabacloud.com\/product\/oceanbase  <\/li>\n<li>Pricing page (verify current URL and region selector): https:\/\/www.alibabacloud.com\/product\/oceanbase\/pricing  <\/li>\n<li>Alibaba Cloud pricing calculator (general): https:\/\/www.alibabacloud.com\/pricing\/calculator<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common pricing dimensions (typical for managed databases)<\/h3>\n\n\n\n<p>Expect pricing to be driven by combinations of:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Compute \/ resources<\/strong>\n   &#8211; vCPU and memory capacity (often purchased as a bundle or \u201cresource units\u201d)\n   &#8211; Tenant or cluster resource allocations (depends on the service\u2019s model)<\/p>\n<\/li>\n<li>\n<p><strong>Storage<\/strong>\n   &#8211; Data storage capacity and type (e.g., SSD-backed)\n   &#8211; IOPS\/performance tiers (if applicable)<\/p>\n<\/li>\n<li>\n<p><strong>Backup storage and retention<\/strong>\n   &#8211; Backup size (full + incremental)\n   &#8211; Retention duration\n   &#8211; Cross-region backup copies (if enabled)<\/p>\n<\/li>\n<li>\n<p><strong>Network<\/strong>\n   &#8211; Cross-AZ traffic is typically internal but can still influence architecture and performance\n   &#8211; Public egress (if you connect from the internet or send data out of Alibaba Cloud)\n   &#8211; Inter-region data transfer for DR\/replication (if used)<\/p>\n<\/li>\n<li>\n<p><strong>Add-ons (if offered)<\/strong>\n   &#8211; Enhanced monitoring, auditing, security features\n   &#8211; Dedicated proxy capacity or additional endpoints\n   &#8211; Migration tools or managed migration services<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<p>Alibaba Cloud offerings change. ApsaraDB for OceanBase may not have a broad free tier like some entry-level services. <strong>Verify in official docs\/pricing<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Main cost drivers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>HA layout<\/strong> (single-zone vs multi-zone; number of replicas)<\/li>\n<li><strong>Provisioned compute<\/strong> (cluster\/tenant sizing)<\/li>\n<li><strong>Storage growth<\/strong> (including indexes and temporary space)<\/li>\n<li><strong>Backups<\/strong> (retention and frequency)<\/li>\n<li><strong>Environment count<\/strong> (dev\/test\/staging\/prod all add up)<\/li>\n<li><strong>Network topology<\/strong> (cross-region DR can materially increase costs)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden or indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ECS bastion hosts<\/strong> used for administration<\/li>\n<li><strong>NAT Gateway<\/strong> if you need outbound internet from private subnets<\/li>\n<li><strong>Log Service (SLS)<\/strong> ingestion\/storage if enabled<\/li>\n<li><strong>Monitoring retention<\/strong> and alerting integrations<\/li>\n<li><strong>Data migration<\/strong> effort (tools, temporary storage, dual-write windows)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost optimization tips (practical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>right-sized tenants<\/strong>: allocate resources where needed; avoid oversizing \u201cjust in case\u201d.<\/li>\n<li>Keep dev\/test small and <strong>short-lived<\/strong>; automate cleanup.<\/li>\n<li>Tune <strong>backup retention<\/strong> to compliance needs, not arbitrary long periods.<\/li>\n<li>Prefer <strong>private VPC connectivity<\/strong> to avoid public egress and reduce attack surface.<\/li>\n<li>Consolidate small workloads into fewer clusters\/tenants where isolation requirements allow.<\/li>\n<li>Track costs by environment tags and enforce budgets\/alerts.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (no fabricated numbers)<\/h3>\n\n\n\n<p>A realistic low-cost lab environment typically includes:\n&#8211; A small ApsaraDB for OceanBase instance\/cluster (smallest supported spec)\n&#8211; Minimal storage and short backup retention\n&#8211; One small ECS instance in the same VPC for testing<\/p>\n\n\n\n<p>Because Alibaba Cloud pricing varies significantly by region and edition, <strong>use the official pricing page and calculator<\/strong> to compute:\n&#8211; hourly\/monthly compute charges\n&#8211; storage charges\n&#8211; backup retention charges<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations (what to model)<\/h3>\n\n\n\n<p>For a production deployment, model:\n&#8211; Multi-zone HA (replica count and zones)\n&#8211; Peak QPS and CPU sizing (plus headroom)\n&#8211; Storage growth (12\u201324 months)\n&#8211; Backup retention and restore testing frequency\n&#8211; DR strategy (same-region vs cross-region)\n&#8211; Observability (logs, metrics, audit) retention<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Provision an <strong>ApsaraDB for OceanBase<\/strong> instance in Alibaba Cloud, create a tenant (MySQL-compatible mode), connect from an ECS host inside the same VPC, run basic SQL, validate monitoring, and then cleanly delete resources to avoid ongoing costs.<\/p>\n\n\n\n<blockquote>\n<p>If your account\/region does not offer MySQL-compatible mode in the console flow you see, adapt the lab to the available mode and follow the official \u201cconnect to database\u201d steps shown in the console. Do not force steps that don\u2019t match your SKU.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Create a VPC and ECS \u201cclient\u201d VM (bastion-style) for private connectivity.\n2. Create an ApsaraDB for OceanBase instance and a tenant.\n3. Configure network access controls (security group + allowlist\/whitelist).\n4. Connect with an SQL client and run basic DDL\/DML.\n5. Validate by checking queries and basic monitoring metrics.\n6. Clean up all created resources.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Prepare networking (VPC, vSwitch, security group)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the <strong>Alibaba Cloud Console<\/strong>, go to <strong>VPC<\/strong>.<\/li>\n<li>Create a <strong>VPC<\/strong> in your target region (choose an RFC1918 CIDR, for example <code>10.0.0.0\/16<\/code>).<\/li>\n<li>Create a <strong>vSwitch<\/strong> in one zone (e.g., <code>10.0.1.0\/24<\/code>).<\/li>\n<li>Create a <strong>Security Group<\/strong> for the ECS client:\n   &#8211; Allow inbound SSH (port 22) <strong>only from your IP<\/strong>.\n   &#8211; Allow outbound internet access (default outbound is typically allowed; verify your org\u2019s baseline rules).<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have a VPC, vSwitch, and security group ready for ECS.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create an ECS client host (for private DB connectivity)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>ECS<\/strong> \u2192 <strong>Instances<\/strong> \u2192 <strong>Create Instance<\/strong>.<\/li>\n<li>Choose:\n   &#8211; The same <strong>region<\/strong> and <strong>VPC\/vSwitch<\/strong> as in Step 1\n   &#8211; A small general-purpose instance type (lab sizing)\n   &#8211; A Linux image (e.g., Alibaba Cloud Linux \/ CentOS \/ Ubuntu)\n   &#8211; The security group from Step 1<\/li>\n<li>Assign a <strong>public IP<\/strong> (EIP or public IPv4) only if you need SSH from your workstation.<br\/>\n   If your organization requires a bastion solution, use that instead.<\/li>\n<li>Create\/choose an SSH key pair or set a strong password (keys preferred).<\/li>\n<li>Connect to the instance:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">ssh -i \/path\/to\/key.pem &lt;username&gt;@&lt;ecs_public_ip&gt;\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"6\">\n<li>Install a MySQL client (commands vary by distro):<\/li>\n<\/ol>\n\n\n\n<p><strong>Ubuntu\/Debian:<\/strong><\/p>\n\n\n\n<pre><code class=\"language-bash\">sudo apt-get update\nsudo apt-get install -y mysql-client\n<\/code><\/pre>\n\n\n\n<p><strong>RHEL\/CentOS\/Alibaba Cloud Linux:<\/strong><\/p>\n\n\n\n<pre><code class=\"language-bash\">sudo yum install -y mysql\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> You can SSH into ECS and have <code>mysql<\/code> client available.<\/p>\n\n\n\n<p><strong>Verification:<\/strong><\/p>\n\n\n\n<pre><code class=\"language-bash\">mysql --version\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create an ApsaraDB for OceanBase instance<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the console, navigate to <strong>ApsaraDB for OceanBase<\/strong>.<\/li>\n<li>Click <strong>Create Instance<\/strong> (wording may vary).<\/li>\n<li>Select:\n   &#8211; <strong>Region<\/strong>: same as your VPC\/ECS\n   &#8211; <strong>Network<\/strong>: choose the VPC and vSwitch you created\n   &#8211; <strong>High availability \/ zones<\/strong>: choose a multi-zone configuration for production-like behavior if available; for a low-cost lab, choose the smallest configuration allowed (always prioritize cost control)\n   &#8211; <strong>Database mode<\/strong>: select <strong>MySQL-compatible mode<\/strong> if offered and you plan to use the <code>mysql<\/code> client in this lab<\/li>\n<li>Review pricing and confirm creation.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> The OceanBase instance enters a \u201cProvisioning\/Creating\u201d state, then becomes \u201cRunning\/Available\u201d.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; Instance status is \u201cRunning\/Available\u201d.\n&#8211; The console shows a <strong>connection endpoint<\/strong> (often proxy endpoint) and a <strong>port<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Create a tenant (and a database user) for the lab<\/h3>\n\n\n\n<p>OceanBase commonly requires working inside a <strong>tenant<\/strong>. In the OceanBase console:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open your created instance.<\/li>\n<li>Go to <strong>Tenants<\/strong> \u2192 <strong>Create Tenant<\/strong> (wording may vary).<\/li>\n<li>\n<p>Choose:\n   &#8211; Tenant mode: <strong>MySQL<\/strong> (or \u201cMySQL-compatible\u201d)\n   &#8211; Resource allocation: select the smallest allowed for the lab\n   &#8211; Admin user\/password for the tenant (store securely)<\/p>\n<\/li>\n<li>\n<p>After the tenant is created, create a database (schema) if the workflow requires it:\n   &#8211; For example, create database <code>labdb<\/code>.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> A tenant exists and is in a healthy state.<\/p>\n\n\n\n<p><strong>Verification:<\/strong>\n&#8211; Tenant status shows healthy\/normal.\n&#8211; Console displays tenant connection details and\/or user naming rules.<\/p>\n\n\n\n<blockquote>\n<p>Connection username formats differ across OceanBase deployments (for example, you may need to include tenant name in the username). <strong>Use the exact connection string and username format shown in your console<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Configure network access (allowlist\/whitelist + security group rules)<\/h3>\n\n\n\n<p>To connect from ECS to the OceanBase instance:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Identify the <strong>private IP<\/strong> of your ECS instance:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">ip addr show\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"2\">\n<li>\n<p>In the ApsaraDB for OceanBase console, find the <strong>network access control<\/strong> section:\n   &#8211; Add the ECS private IP (or the vSwitch CIDR) to the allowed list\/whitelist, if required.\n   &#8211; Prefer <strong>CIDR-based allowlisting<\/strong> for the subnet rather than single IPs if your ECS IP may change.<\/p>\n<\/li>\n<li>\n<p>Ensure security groups and VPC routing allow:\n   &#8211; ECS \u2192 OceanBase endpoint on the required port (use the port shown in console)<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> Network policy permits ECS to connect to the OceanBase endpoint.<\/p>\n\n\n\n<p><strong>Verification (basic TCP check):<\/strong>\nIf <code>nc<\/code> is available:<\/p>\n\n\n\n<pre><code class=\"language-bash\">nc -vz &lt;oceanbase_endpoint&gt; &lt;port&gt;\n<\/code><\/pre>\n\n\n\n<p>If <code>nc<\/code> is not installed, install it or proceed to the MySQL client connection and interpret errors.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Connect to OceanBase from ECS and run SQL<\/h3>\n\n\n\n<p>On the ECS host, connect using the endpoint\/port from the console.<\/p>\n\n\n\n<p>Example (adjust to what your console shows):<\/p>\n\n\n\n<pre><code class=\"language-bash\">mysql -h &lt;oceanbase_endpoint&gt; -P &lt;port&gt; -u &lt;username&gt; -p\n<\/code><\/pre>\n\n\n\n<p>After login, run:<\/p>\n\n\n\n<pre><code class=\"language-sql\">SELECT VERSION();\nSHOW DATABASES;\n<\/code><\/pre>\n\n\n\n<p>Create a database and table (if not already created in the console flow):<\/p>\n\n\n\n<pre><code class=\"language-sql\">CREATE DATABASE IF NOT EXISTS labdb;\nUSE labdb;\n\nCREATE TABLE IF NOT EXISTS orders (\n  id BIGINT PRIMARY KEY,\n  user_id BIGINT NOT NULL,\n  amount_cents BIGINT NOT NULL,\n  status VARCHAR(32) NOT NULL,\n  created_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP\n);\n\nINSERT INTO orders (id, user_id, amount_cents, status)\nVALUES\n  (1, 101, 2599, 'CREATED'),\n  (2, 102, 4999, 'PAID');\n\nSELECT * FROM orders ORDER BY id;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> You can connect successfully and query the inserted rows.<\/p>\n\n\n\n<p><strong>Verification checklist:<\/strong>\n&#8211; <code>SELECT VERSION();<\/code> returns an OceanBase version string (or a compatible version string).\n&#8211; <code>SELECT * FROM orders;<\/code> returns two rows.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: Validate basic monitoring in the console<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Return to the Alibaba Cloud console \u2192 your OceanBase instance.<\/li>\n<li>Open <strong>Monitoring \/ Performance<\/strong> (naming varies).<\/li>\n<li>Check that you can see:\n   &#8211; Connections\n   &#8211; QPS\/TPS (or similar)\n   &#8211; CPU\/memory usage<\/li>\n<li>(Optional) Generate a little load:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">mysql -h &lt;endpoint&gt; -P &lt;port&gt; -u &lt;user&gt; -p -e \"USE labdb; SELECT COUNT(*) FROM orders;\"\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> Monitoring charts show recent activity and stable resource usage.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use this quick validation sequence:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Connectivity:<\/strong> <code>mysql<\/code> login works from ECS.<\/li>\n<li><strong>SQL correctness:<\/strong> DDL\/DML executed successfully.<\/li>\n<li><strong>Data persistence:<\/strong> Reconnect and re-run:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-sql\">USE labdb;\nSELECT COUNT(*) FROM orders;\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"4\">\n<li><strong>Console health:<\/strong> Instance and tenant show healthy state; monitoring shows activity.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p>Common issues and fixes:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Access denied \/ authentication errors<\/strong>\n   &#8211; Confirm you are using the <strong>exact username format<\/strong> required for your tenant.\n   &#8211; Reset the tenant user password in the console if needed.\n   &#8211; Verify you are connecting to the correct endpoint\/port for the tenant.<\/p>\n<\/li>\n<li>\n<p><strong>Connection timeout<\/strong>\n   &#8211; Most commonly caused by allowlist\/whitelist not including ECS IP\/CIDR.\n   &#8211; Verify security group rules and that the endpoint is reachable inside the VPC.\n   &#8211; Confirm ECS is in the same VPC (or has proper network connectivity via peering\/VPN\/Express Connect).<\/p>\n<\/li>\n<li>\n<p><strong>Unknown database \/ permission denied<\/strong>\n   &#8211; Ensure you created <code>labdb<\/code> and ran <code>USE labdb;<\/code>\n   &#8211; Ensure the user has privileges on the database.\n   &#8211; In managed services, \u201croot\u201d\/superuser behavior may be restricted; follow the tenant admin patterns.<\/p>\n<\/li>\n<li>\n<p><strong>Port confusion<\/strong>\n   &#8211; Use the <strong>port shown in the ApsaraDB for OceanBase console<\/strong>. Do not assume default MySQL port 3306.<\/p>\n<\/li>\n<li>\n<p><strong>Can\u2019t see monitoring metrics<\/strong>\n   &#8211; Metrics may take several minutes to appear.\n   &#8211; Verify you have RAM permission to view monitoring.\n   &#8211; Verify integration with CloudMonitor if it is a separate enablement step (depends on product behavior).<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing charges, delete resources in the reverse order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Delete tenant(s)<\/strong> (if the console requires tenant deletion before instance deletion).<\/li>\n<li><strong>Delete the ApsaraDB for OceanBase instance<\/strong> from the console.<\/li>\n<li><strong>Delete ECS instance<\/strong> used for testing.<\/li>\n<li><strong>Release public IP\/EIP<\/strong> (if allocated separately).<\/li>\n<li><strong>Delete security group<\/strong> (if dedicated to the lab).<\/li>\n<li><strong>Delete vSwitch and VPC<\/strong> (only if they were created solely for this lab).<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> No billable OceanBase\/ECS resources remain.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Use multi-zone deployments<\/strong> for production HA whenever available and aligned with your RPO\/RTO.<\/li>\n<li>Design for <strong>failure domains<\/strong>: assume a node or zone can fail; keep applications stateless and retry-safe.<\/li>\n<li>Separate workloads using <strong>tenants<\/strong> (or separate instances) based on:<\/li>\n<li>compliance boundaries<\/li>\n<li>performance isolation needs<\/li>\n<li>blast-radius reduction<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices (RAM)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enforce least privilege:<\/li>\n<li>Separate roles for \u201cDB platform admin\u201d vs \u201cread-only auditor\u201d vs \u201capp operator\u201d.<\/li>\n<li>Use RAM policies to prevent accidental deletes:<\/li>\n<li>Restrict delete actions to break-glass roles.<\/li>\n<li>Require MFA and strong password policies for console administrators.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Right-size tenants; avoid \u201cone huge tenant for everything\u201d unless you must.<\/li>\n<li>Use <strong>budgets and alerts<\/strong> to detect unexpected scale or backup growth.<\/li>\n<li>Keep dev\/test environments small and automate cleanup.<\/li>\n<li>Be deliberate about backup retention and DR replication (these can be major cost multipliers).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Benchmark with realistic workloads before production.<\/li>\n<li>Review schema design:<\/li>\n<li>choose appropriate primary keys and indexes<\/li>\n<li>avoid unbounded hot keys<\/li>\n<li>Monitor slow queries and connection counts; tune application pooling.<\/li>\n<li>Keep large batch jobs off peak; consider separate tenants for heavy jobs if isolation is needed.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Implement app-side retry with backoff for transient errors.<\/li>\n<li>Test restore procedures regularly (table-level vs database-level restore capability depends on product features).<\/li>\n<li>Document RTO steps and owners: what to do during zone failover events.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Define SLOs (latency, availability, error budgets).<\/li>\n<li>Create runbooks:<\/li>\n<li>connectivity failures<\/li>\n<li>high CPU\/memory<\/li>\n<li>storage nearing capacity<\/li>\n<li>replication lag (if metrics exist)<\/li>\n<li>Standardize naming:<\/li>\n<li><code>env-app-region-purpose<\/code> for instances and tenants.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use Alibaba Cloud tags for:<\/li>\n<li><code>env<\/code> (dev\/stage\/prod)<\/li>\n<li><code>owner<\/code><\/li>\n<li><code>cost-center<\/code><\/li>\n<li><code>data-classification<\/code><\/li>\n<li>Maintain a CMDB-style record: endpoint, tenant names, critical tables, restore policy, on-call rotation.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>RAM controls<\/strong> who can create\/modify\/delete OceanBase resources in the cloud control plane.<\/li>\n<li><strong>Database users\/roles<\/strong> control SQL access within a tenant\/database.<\/li>\n<li>Best practice: separate admin identities:<\/li>\n<li>Cloud resource admins (RAM)<\/li>\n<li>Database admins (tenant admin)<\/li>\n<li>Application users (least privilege)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>In transit:<\/strong> Prefer TLS if supported for client connections; verify how to enable and enforce it for your edition.<\/li>\n<li><strong>At rest:<\/strong> Managed services commonly encrypt storage; verify configuration options and whether you can use <strong>KMS<\/strong> keys (customer-managed keys) or only service-managed encryption.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prefer <strong>VPC-only private endpoints<\/strong> for production.<\/li>\n<li>If public access is enabled:<\/li>\n<li>strict IP allowlisting<\/li>\n<li>TLS-only connections<\/li>\n<li>rotate credentials regularly<\/li>\n<li>monitor auth failures<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Never store DB passwords in source code.<\/li>\n<li>Use a secrets manager pattern (Alibaba Cloud secrets services vary; verify current recommended product).<\/li>\n<li>Rotate credentials and use separate credentials per application\/service.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable audit logs if available.<\/li>\n<li>Centralize logs into <strong>Log Service (SLS)<\/strong> where possible.<\/li>\n<li>Ensure logs do not contain sensitive data (PII) or redact at the app layer.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Choose region based on data residency requirements.<\/li>\n<li>Document backup retention and encryption settings.<\/li>\n<li>Enforce least privilege and maintain access review processes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Opening DB endpoints to <code>0.0.0.0\/0<\/code><\/li>\n<li>Reusing tenant admin credentials across multiple apps<\/li>\n<li>Over-permissive RAM policies (e.g., granting delete instance to many users)<\/li>\n<li>No monitoring of login failures and abnormal connection patterns<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Private access + strict allowlist<\/li>\n<li>Separate tenants by environment and sensitivity<\/li>\n<li>Enable monitoring\/alerts for:<\/li>\n<li>abnormal connections<\/li>\n<li>privilege changes (if auditable)<\/li>\n<li>backup failures<\/li>\n<li>Use change management for parameter\/scale operations<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<blockquote>\n<p>Confirm all limits in official documentation for your region\/edition.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Known limitations (typical categories)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Compatibility gaps:<\/strong> MySQL\/Oracle-compatible modes may not support every feature, function, or edge-case behavior.<\/li>\n<li><strong>Operational constraints:<\/strong> Some scaling or topology changes may require maintenance windows or have performance impacts.<\/li>\n<li><strong>Tenant complexity:<\/strong> Mis-sizing tenants can cause throttling or noisy-neighbor effects.<\/li>\n<li><strong>Connection semantics:<\/strong> Username formats and endpoint behavior can differ from standard single-node MySQL.<\/li>\n<li><strong>Tooling differences:<\/strong> Some third-party tools may require special connection parameters.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Instance count per region<\/li>\n<li>Tenant count per instance<\/li>\n<li>Max connections \/ max sessions<\/li>\n<li>Storage caps and backup retention limits<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regional constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some regions may not support certain HA layouts, modes, or features.<\/li>\n<li>Cross-region DR (if available) may be limited to certain region pairs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing surprises<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Backup retention storage can grow significantly (full + incremental).<\/li>\n<li>DR replication and cross-region data transfer can add substantial cost.<\/li>\n<li>Observability (logs\/metrics retention) can be non-trivial at scale.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compatibility issues<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SQL syntax differences (especially Oracle mode)<\/li>\n<li>Differences in transaction isolation edge cases<\/li>\n<li>Stored procedures\/functions support varies by mode\/version (verify)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational gotchas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Allowlist\/whitelist issues are the #1 connectivity blocker.<\/li>\n<li>Under-provisioned proxy capacity can look like \u201cDB is slow\u201d when the bottleneck is connection routing.<\/li>\n<li>Schema changes on large tables can be expensive; plan online schema change strategies and test.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Migration challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data type mapping and character set\/collation differences<\/li>\n<li>Sequence\/identity semantics differences (Oracle mode vs MySQL mode)<\/li>\n<li>Cutover planning: dual writes, CDC, consistency validation<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Vendor-specific nuances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OceanBase uses distributed concepts (tenants, partitions, replicas) that require different mental models than single-node MySQL.<\/li>\n<li>Some \u201cDBA\u201d tasks are done differently; invest in training and runbooks.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>ApsaraDB for OceanBase fits a specific \u201cdistributed relational OLTP\u201d niche. Compare it to other Alibaba Cloud database services and to other cloud-native distributed databases.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>ApsaraDB for OceanBase (Alibaba Cloud)<\/strong><\/td>\n<td>Large-scale OLTP, strong consistency, enterprise migrations<\/td>\n<td>Distributed design, HA across zones, managed service, compatibility modes (verify)<\/td>\n<td>Requires distributed DB know-how; compatibility not perfect; pricing can be complex<\/td>\n<td>When you need a managed distributed relational DB on Alibaba Cloud<\/td>\n<\/tr>\n<tr>\n<td><strong>ApsaraDB RDS (Alibaba Cloud)<\/strong><\/td>\n<td>Standard MySQL\/PostgreSQL\/SQL Server workloads<\/td>\n<td>Simplicity, broad ecosystem compatibility, straightforward operations<\/td>\n<td>Vertical scaling limits; may need sharding at very large scale<\/td>\n<td>When single-node managed DB is sufficient and you want simplicity<\/td>\n<\/tr>\n<tr>\n<td><strong>PolarDB (Alibaba Cloud)<\/strong><\/td>\n<td>Cloud-native relational with high performance and read scaling<\/td>\n<td>Strong performance options; managed; read scaling patterns<\/td>\n<td>Architecture differs from distributed multi-master designs; choose based on workload<\/td>\n<td>When you want managed relational with strong read scaling and simpler migration<\/td>\n<\/tr>\n<tr>\n<td><strong>AnalyticDB (Alibaba Cloud)<\/strong><\/td>\n<td>Analytics\/OLAP workloads<\/td>\n<td>Columnar analytics and query performance<\/td>\n<td>Not a drop-in OLTP store<\/td>\n<td>When analytics is the primary workload<\/td>\n<\/tr>\n<tr>\n<td><strong>Self-managed OceanBase \/ Community Edition<\/strong><\/td>\n<td>Maximum control and customization<\/td>\n<td>Full control over configs and deployment<\/td>\n<td>Highest ops burden; HA, backups, upgrades are your responsibility<\/td>\n<td>When you must self-host or need custom topology\/tooling<\/td>\n<\/tr>\n<tr>\n<td><strong>Amazon Aurora \/ RDS<\/strong><\/td>\n<td>AWS-managed relational workloads<\/td>\n<td>Mature managed service ecosystem<\/td>\n<td>Not Alibaba Cloud; migration and network considerations<\/td>\n<td>When your platform is AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Cloud Spanner<\/strong><\/td>\n<td>Globally distributed relational with strong consistency<\/td>\n<td>Global scalability; strong consistency<\/td>\n<td>Different SQL\/features; cost model; lock-in<\/td>\n<td>When you need global distribution and can adopt Spanner model<\/td>\n<\/tr>\n<tr>\n<td><strong>CockroachDB \/ YugabyteDB (self-managed or managed)<\/strong><\/td>\n<td>Cloud-agnostic distributed SQL<\/td>\n<td>Multi-cloud options<\/td>\n<td>Operational and feature tradeoffs; cost<\/td>\n<td>When you need distributed SQL outside Alibaba Cloud<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: Payment and billing platform modernization<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A regional payment provider runs a legacy MySQL cluster with manual sharding and complex failover scripts. Growth increases operational incidents and slows new feature delivery.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Multi-zone ApsaraDB for OceanBase deployment in a core region<\/li>\n<li>Separate tenants for payment ledger, billing, and reconciliation workloads<\/li>\n<li>Private VPC connectivity from microservices on ECS\/ACK<\/li>\n<li>Centralized monitoring and alerting; scheduled backups; tested restores<\/li>\n<li><strong>Why ApsaraDB for OceanBase was chosen:<\/strong><\/li>\n<li>Need distributed OLTP scale with strong consistency<\/li>\n<li>Reduce sharding complexity and operational toil<\/li>\n<li>Managed HA and backups align with compliance requirements<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Reduced failover complexity and improved availability<\/li>\n<li>Faster scaling for peak events<\/li>\n<li>Improved operational visibility and standardized runbooks<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: Rapidly scaling SaaS with tenant isolation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A SaaS startup outgrows a single MySQL instance; large customers require performance isolation and stricter operational controls.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>ApsaraDB for OceanBase instance with multiple tenants:<ul>\n<li>shared tenant for small customers<\/li>\n<li>dedicated tenant for top-tier customers<\/li>\n<\/ul>\n<\/li>\n<li>ECS-based app tier with strict secret management and private VPC connectivity<\/li>\n<li>Cost monitoring with tags and budget alerts<\/li>\n<li><strong>Why ApsaraDB for OceanBase was chosen:<\/strong><\/li>\n<li>Avoid building and operating sharding middleware<\/li>\n<li>Use tenant isolation for tiered offerings<\/li>\n<li>Keep DB operations manageable for a small team<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Ability to onboard larger customers without re-architecting DB sharding<\/li>\n<li>Better performance isolation and clearer cost allocation<\/li>\n<li>More predictable operations with managed backups and monitoring<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>Is ApsaraDB for OceanBase a MySQL database?<\/strong><br\/>\nIt is a managed service based on the OceanBase database engine, which commonly offers <strong>MySQL-compatible mode<\/strong>. Compatibility is not necessarily identical to MySQL in every feature and edge case\u2014test your workload.<\/p>\n\n\n\n<p>2) <strong>Does it support Oracle workloads?<\/strong><br\/>\nOceanBase often provides <strong>Oracle-compatible mode<\/strong>. The degree of compatibility (SQL features, packages, procedures) depends on edition\/version\u2014verify in official docs and run a PoC.<\/p>\n\n\n\n<p>3) <strong>Is it a globally distributed database?<\/strong><br\/>\nApsaraDB for OceanBase is typically <strong>region-scoped<\/strong> with <strong>multi-zone<\/strong> HA within a region. Cross-region DR may exist but is not the same as \u201cactive-active global\u201d by default\u2014verify.<\/p>\n\n\n\n<p>4) <strong>How do I connect to it?<\/strong><br\/>\nYou use the endpoint and port shown in the Alibaba Cloud console, typically through a proxy endpoint. Use the driver compatible with your selected mode (MySQL\/Oracle).<\/p>\n\n\n\n<p>5) <strong>Do I need an ECS instance to connect?<\/strong><br\/>\nNot strictly, but for private VPC deployments it\u2019s the simplest way to test connectivity. In production, your application tier typically connects from ECS\/ACK within the same VPC.<\/p>\n\n\n\n<p>6) <strong>What is a tenant in OceanBase?<\/strong><br\/>\nA tenant is a logical isolation boundary inside a cluster\/instance, often with its own resources and users. It\u2019s used to separate workloads and manage resource governance.<\/p>\n\n\n\n<p>7) <strong>Is it suitable for small dev databases?<\/strong><br\/>\nIt can be, but it may be overkill compared to simpler managed databases. Choose it if you need distributed scale or want early alignment with your production platform.<\/p>\n\n\n\n<p>8) <strong>How do backups work?<\/strong><br\/>\nManaged backups are configured via console policies. Details vary (full\/incremental, PITR support, retention). Always test restores and verify RTO.<\/p>\n\n\n\n<p>9) <strong>Can I enable encryption with my own keys?<\/strong><br\/>\nSome Alibaba Cloud managed databases integrate with KMS for customer-managed keys; availability depends on the product and region. Verify in the OceanBase documentation.<\/p>\n\n\n\n<p>10) <strong>Does OceanBase support read replicas?<\/strong><br\/>\nOceanBase uses replicas as part of its distributed architecture. Read scaling and routing depend on the proxy and configuration. Confirm read\/write routing options in official docs.<\/p>\n\n\n\n<p>11) <strong>What are the most common causes of connection failures?<\/strong><br\/>\nIncorrect allowlist\/whitelist, wrong endpoint\/port, wrong username format for the tenant, and security group restrictions.<\/p>\n\n\n\n<p>12) <strong>How do I migrate from MySQL or Oracle?<\/strong><br\/>\nPlan a migration with schema assessment, compatibility testing, data migration tooling, and cutover strategy (CDC\/dual-write). Alibaba Cloud may provide migration tools\u2014verify the recommended toolchain for OceanBase.<\/p>\n\n\n\n<p>13) <strong>Is ApsaraDB for OceanBase serverless?<\/strong><br\/>\nIt is generally provisioned as a managed instance\/cluster with allocated resources. If a serverless option exists, it will be explicit in the pricing\/console\u2014verify.<\/p>\n\n\n\n<p>14) <strong>How do I monitor performance?<\/strong><br\/>\nUse the OceanBase console monitoring pages and CloudMonitor alarms where supported. Track latency, QPS\/TPS, connections, CPU\/memory, and slow queries.<\/p>\n\n\n\n<p>15) <strong>Can I use it with Kubernetes (ACK)?<\/strong><br\/>\nYes, commonly via private VPC connectivity from pods to the OceanBase endpoint. Ensure network policies, DNS, and secrets are configured properly.<\/p>\n\n\n\n<p>16) <strong>How do I design for high availability?<\/strong><br\/>\nUse multi-zone deployments, keep applications retry-safe, use stable endpoints, and test failover behavior in staging.<\/p>\n\n\n\n<p>17) <strong>When should I choose PolarDB or RDS instead?<\/strong><br\/>\nChoose RDS\/PolarDB when you want simpler operations, maximum compatibility with MySQL\/PostgreSQL, or when your workload doesn\u2019t require distributed scale.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn ApsaraDB for OceanBase<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official product page<\/td>\n<td>Alibaba Cloud OceanBase product page \u2014 https:\/\/www.alibabacloud.com\/product\/oceanbase<\/td>\n<td>High-level overview, positioning, and entry points to docs\/pricing<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>ApsaraDB for OceanBase documentation \u2014 https:\/\/www.alibabacloud.com\/help\/en\/apsaradb-for-oceanbase<\/td>\n<td>Primary source for concepts, features, operations, and how-to steps<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>OceanBase pricing \u2014 https:\/\/www.alibabacloud.com\/product\/oceanbase\/pricing<\/td>\n<td>Region\/SKU pricing model details (verify region selector)<\/td>\n<\/tr>\n<tr>\n<td>Pricing calculator<\/td>\n<td>Alibaba Cloud Pricing Calculator \u2014 https:\/\/www.alibabacloud.com\/pricing\/calculator<\/td>\n<td>Build estimates including compute\/storage\/network<\/td>\n<\/tr>\n<tr>\n<td>Official tutorials\/getting started<\/td>\n<td>OceanBase \u201cGetting Started\u201d section (in docs) \u2014 https:\/\/www.alibabacloud.com\/help\/en\/apsaradb-for-oceanbase<\/td>\n<td>Step-by-step creation, connection, and basic operations<\/td>\n<\/tr>\n<tr>\n<td>Official architecture guidance<\/td>\n<td>Alibaba Cloud Architecture Center \u2014 https:\/\/www.alibabacloud.com\/architecture<\/td>\n<td>Reference architectures and cloud best practices (search for OceanBase patterns)<\/td>\n<\/tr>\n<tr>\n<td>OceanBase community\/product docs (engine-level)<\/td>\n<td>OceanBase documentation \u2014 https:\/\/en.oceanbase.com\/docs (verify current docs site)<\/td>\n<td>Engine concepts (tenants, partitions, proxies) and SQL behavior (confirm alignment with managed service version)<\/td>\n<\/tr>\n<tr>\n<td>GitHub (engine\/community)<\/td>\n<td>OceanBase GitHub \u2014 https:\/\/github.com\/oceanbase<\/td>\n<td>Source\/community examples; useful for understanding tooling (verify applicability to managed service)<\/td>\n<\/tr>\n<tr>\n<td>Observability docs<\/td>\n<td>Alibaba Cloud CloudMonitor docs \u2014 https:\/\/www.alibabacloud.com\/help\/en\/cloudmonitor<\/td>\n<td>Set up alarms\/dashboards around managed database metrics<\/td>\n<\/tr>\n<tr>\n<td>Networking docs<\/td>\n<td>Alibaba Cloud VPC docs \u2014 https:\/\/www.alibabacloud.com\/help\/en\/vpc<\/td>\n<td>Required for private connectivity design and troubleshooting<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, SREs, platform teams<\/td>\n<td>Cloud operations, DevOps practices, deployment automation (check OceanBase coverage)<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Beginners to intermediate engineers<\/td>\n<td>DevOps\/SCM fundamentals, tooling and practices<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud engineers, operations teams<\/td>\n<td>Cloud operations and troubleshooting<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, reliability engineers<\/td>\n<td>SRE principles, monitoring, incident response<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops\/SRE teams exploring AIOps<\/td>\n<td>AIOps concepts, automation for ops<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>Cloud\/DevOps training content (verify specific offerings)<\/td>\n<td>Engineers seeking guided learning paths<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training and mentoring (verify course catalog)<\/td>\n<td>Beginners to intermediate DevOps learners<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps services\/training (verify offerings)<\/td>\n<td>Teams needing short-term help or coaching<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support and training resources (verify services)<\/td>\n<td>Ops teams needing practical support<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company Name<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify portfolio)<\/td>\n<td>Cloud architecture, migrations, operations<\/td>\n<td>VPC design, CI\/CD setup, observability improvements<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps consulting and training (verify offerings)<\/td>\n<td>Delivery pipelines, SRE practices, platform enablement<\/td>\n<td>Implement monitoring\/alerting, operational runbooks<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify offerings)<\/td>\n<td>Automation, cloud operations<\/td>\n<td>Infrastructure automation, security hardening, deployment workflows<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before ApsaraDB for OceanBase<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Relational database fundamentals<\/strong><\/li>\n<li>SQL, indexing, transactions, isolation levels<\/li>\n<li><strong>MySQL and\/or Oracle basics<\/strong><\/li>\n<li>schema design, query plans, user\/role management<\/li>\n<li><strong>Alibaba Cloud fundamentals<\/strong><\/li>\n<li>VPC, ECS, RAM, security groups, CloudMonitor<\/li>\n<li><strong>Networking basics<\/strong><\/li>\n<li>CIDR, routing, private endpoints, VPN\/Express Connect concepts<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after ApsaraDB for OceanBase<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OceanBase internals (tenants, partitioning, replication concepts)<\/li>\n<li>Migration engineering<\/li>\n<li>compatibility assessment<\/li>\n<li>data validation strategies<\/li>\n<li>CDC-based cutovers<\/li>\n<li>Advanced observability (SLOs, alert tuning, capacity planning)<\/li>\n<li>Performance engineering<\/li>\n<li>query tuning, schema evolution strategies, load testing<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud database engineer \/ DBA (managed services)<\/li>\n<li>Platform engineer (database platform ownership)<\/li>\n<li>SRE \/ reliability engineer (database SLOs and incident response)<\/li>\n<li>Solutions architect (workload selection and HA\/cost design)<\/li>\n<li>DevOps engineer (CI\/CD + database change management)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Alibaba Cloud certification catalogs change. Check Alibaba Cloud\u2019s official certification and training pages and look for OceanBase content:\n&#8211; Alibaba Cloud Training &amp; Certification: https:\/\/www.alibabacloud.com\/training<br\/>\nIf there is no OceanBase-specific certification, target:\n&#8211; Alibaba Cloud associate\/professional cloud certifications\n&#8211; Database fundamentals certifications (vendor-neutral) and then specialize via OceanBase docs and labs<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build a simple order service (API + SQL schema) and run load tests from ECS<\/li>\n<li>Implement database migration: MySQL \u2192 OceanBase (schema + data + validation scripts)<\/li>\n<li>Create monitoring dashboards and alerts for latency and error budget burn<\/li>\n<li>Design a multi-tenant SaaS schema and simulate noisy neighbor scenarios<\/li>\n<li>Practice backup\/restore runbooks and measure RTO<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ApsaraDB<\/strong>: Alibaba Cloud\u2019s managed database product family.<\/li>\n<li><strong>OceanBase<\/strong>: A distributed relational database engine used by ApsaraDB for OceanBase.<\/li>\n<li><strong>Region<\/strong>: A geographic area where Alibaba Cloud resources are deployed.<\/li>\n<li><strong>Zone<\/strong>: An isolated location within a region (separate power\/network\/cooling).<\/li>\n<li><strong>VPC (Virtual Private Cloud)<\/strong>: A logically isolated private network in Alibaba Cloud.<\/li>\n<li><strong>vSwitch<\/strong>: A subnet within a VPC, scoped to a zone.<\/li>\n<li><strong>Security Group<\/strong>: Virtual firewall controlling inbound\/outbound traffic for ECS and some services.<\/li>\n<li><strong>Tenant<\/strong>: A logical isolation boundary within OceanBase, often used for resource and workload separation.<\/li>\n<li><strong>Proxy endpoint (OBProxy\/ODP)<\/strong>: A routing layer that provides a stable connection endpoint for a distributed database.<\/li>\n<li><strong>Allowlist\/Whitelist<\/strong>: Network access control list of allowed IPs or CIDR blocks.<\/li>\n<li><strong>RAM (Resource Access Management)<\/strong>: Alibaba Cloud IAM service for identities, roles, and permissions.<\/li>\n<li><strong>CloudMonitor<\/strong>: Alibaba Cloud monitoring and alerting service.<\/li>\n<li><strong>SLS (Log Service)<\/strong>: Alibaba Cloud centralized logging service.<\/li>\n<li><strong>OSS (Object Storage Service)<\/strong>: Alibaba Cloud object storage, commonly used for backups and data lakes.<\/li>\n<li><strong>RPO (Recovery Point Objective)<\/strong>: Maximum acceptable data loss measured in time.<\/li>\n<li><strong>RTO (Recovery Time Objective)<\/strong>: Maximum acceptable downtime to restore service.<\/li>\n<li><strong>OLTP<\/strong>: Online Transaction Processing; transaction-heavy workloads.<\/li>\n<li><strong>OLAP<\/strong>: Online Analytical Processing; analytics-heavy workloads.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>ApsaraDB for OceanBase is Alibaba Cloud\u2019s managed distributed relational database service in the <strong>Databases<\/strong> category. It is designed for teams that need <strong>high availability, strong consistency, and horizontal scalability<\/strong> for OLTP workloads, often with <strong>MySQL-compatible and\/or Oracle-compatible<\/strong> access modes (verify exact compatibility for your edition\/region).<\/p>\n\n\n\n<p>It matters because it can reduce the operational burden and risk of running a distributed database while enabling architectures that outgrow single-node relational databases. Cost planning should focus on <strong>provisioned compute, HA layout, storage growth, and backup\/DR retention<\/strong>, while security planning should prioritize <strong>private VPC connectivity, least-privilege RAM policies, strict network allowlists, and credential hygiene<\/strong>.<\/p>\n\n\n\n<p>Use it when you need a managed distributed relational backend on Alibaba Cloud and you\u2019re prepared to validate SQL compatibility and operate with tenants, zones, and proxy endpoints. Next steps: follow the official documentation, replicate the lab in a staging environment, and run a realistic performance and migration proof of concept using your real schema and queries.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Databases<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,12],"tags":[],"class_list":["post-76","post","type-post","status-publish","format-standard","hentry","category-alibaba-cloud","category-databases"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/76","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=76"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/76\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=76"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=76"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=76"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}