{"id":71,"date":"2026-04-12T17:39:14","date_gmt":"2026-04-12T17:39:14","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-polardb-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-databases\/"},"modified":"2026-04-12T17:39:14","modified_gmt":"2026-04-12T17:39:14","slug":"alibaba-cloud-polardb-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-databases","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/alibaba-cloud-polardb-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-databases\/","title":{"rendered":"Alibaba Cloud PolarDB 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>PolarDB is a managed relational database service in <strong>Alibaba Cloud Databases<\/strong> designed for high availability, scalability, and operational simplicity. It provides database engines that are compatible with popular open-source and commercial ecosystems (for example MySQL-compatible and PostgreSQL-compatible options), while Alibaba Cloud manages the underlying infrastructure, backups, patching (scope varies by offering), and failover capabilities.<\/p>\n\n\n\n<p>In simple terms: <strong>PolarDB lets you run a production-grade relational database cluster without building and operating your own MySQL\/PostgreSQL\/Oracle-like database stack<\/strong>. You provision a cluster, get endpoints for applications, and scale read capacity by adding read-only nodes while relying on built-in resiliency and backup features.<\/p>\n\n\n\n<p>Technically, PolarDB is implemented as a <strong>database cluster<\/strong> with <strong>compute nodes<\/strong> (database instances) and <strong>shared storage<\/strong> (architecture depends on engine\/edition). Applications connect through PolarDB endpoints inside a VPC, and the cluster can include a primary (read\/write) node and one or more read-only nodes for read scaling and high availability. You manage it through the Alibaba Cloud console and APIs, and you can integrate with services like <strong>Data Management (DMS)<\/strong> and monitoring tools (for example <strong>Database Autonomy Service (DAS)<\/strong>, where supported).<\/p>\n\n\n\n<p>PolarDB solves common problems teams face with self-managed databases: <strong>manual replication setup, complex failover, slow scaling for reads, operational toil (backups\/patching), and difficulty achieving consistent performance and availability<\/strong>\u2014while still preserving a familiar SQL interface and compatibility with widely used tools and drivers.<\/p>\n\n\n\n<blockquote>\n<p>Service naming note: <strong>PolarDB<\/strong> is the product name in Alibaba Cloud. Alibaba Cloud also offers related-but-separate database products (for example <strong>ApsaraDB RDS<\/strong> and <strong>PolarDB-X<\/strong>). This tutorial focuses only on <strong>PolarDB<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is PolarDB?<\/h2>\n\n\n\n<p>PolarDB is Alibaba Cloud\u2019s managed relational database service that provides database clusters with high availability, read scaling, backup\/restore capabilities, and compatibility with common SQL ecosystems.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose (scope-aligned)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provide <strong>managed relational database clusters<\/strong> for production workloads.<\/li>\n<li>Offer <strong>high availability<\/strong> and <strong>scaling<\/strong> while reducing day-2 operational work (backups, monitoring integrations, failover mechanisms).<\/li>\n<li>Support <strong>engine compatibility options<\/strong> (such as MySQL-compatible and PostgreSQL-compatible offerings; additional compatibility modes may exist\u2014verify in official docs for your region\/edition).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cluster-based deployment with endpoints for application connectivity.<\/li>\n<li>High availability through multi-node architecture and automated failover (exact behavior depends on engine\/edition\u2014verify in official docs).<\/li>\n<li>Read scaling using read-only nodes (where supported).<\/li>\n<li>Automated backups and point-in-time recovery (PITR) options (retention, backup types, and restore granularity vary\u2014verify).<\/li>\n<li>Monitoring and performance insights via Alibaba Cloud\u2019s ecosystem tools (for example DAS, CloudMonitor).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PolarDB Cluster<\/strong>: The top-level resource you create and manage.<\/li>\n<li><strong>Primary (read\/write) node<\/strong>: Handles writes and read\/write traffic.<\/li>\n<li><strong>Read-only node(s)<\/strong>: Scale out reads and may support failover scenarios.<\/li>\n<li><strong>Endpoints<\/strong>: Connection addresses (for example, a cluster endpoint; additional endpoints may exist depending on engine\/edition).<\/li>\n<li><strong>Storage layer<\/strong>: Managed storage used by the cluster (details vary by engine\/edition).<\/li>\n<li><strong>Backup and snapshots<\/strong>: Automated and manual backup mechanisms.<\/li>\n<li><strong>Networking<\/strong>: VPC access, whitelists, security groups (at the VPC level), SSL\/TLS options.<\/li>\n<\/ul>\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 relational database service (DBaaS)<\/strong> in the <strong>Databases<\/strong> category.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope (regional\/zonal\/account)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PolarDB is typically <strong>region-scoped<\/strong> (you choose a region when creating a cluster).<\/li>\n<li>High availability is commonly implemented across <strong>zones<\/strong> within a region (multi-zone options vary by region and offering\u2014verify in official docs and console).<\/li>\n<li>It is <strong>account-scoped<\/strong> within your Alibaba Cloud account; access is controlled by <strong>RAM<\/strong> (Resource Access Management) and network controls (VPC).<\/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>PolarDB is commonly used with:\n&#8211; <strong>ECS (Elastic Compute Service)<\/strong> for application servers and database clients.\n&#8211; <strong>VPC<\/strong> for private networking and isolation.\n&#8211; <strong>SLB (Server Load Balancer)<\/strong> \/ <strong>ALB<\/strong> for application entry points (not for database traffic).\n&#8211; <strong>DMS (Data Management)<\/strong> for database administration, SQL execution, change management, and access control workflows.\n&#8211; <strong>DAS (Database Autonomy Service)<\/strong> for performance diagnostics and insights (availability varies\u2014verify).\n&#8211; <strong>ActionTrail<\/strong> for auditing control-plane API actions.\n&#8211; <strong>KMS<\/strong> for encryption key management (when encryption features integrate with KMS\u2014verify by engine\/edition).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use PolarDB?<\/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>Faster time to production<\/strong>: You can provision a cluster in minutes instead of building replication, backups, and failover from scratch.<\/li>\n<li><strong>Lower operational overhead<\/strong>: Managed backups, automated health management, and integrated monitoring reduce DBA\/SRE burden.<\/li>\n<li><strong>Predictable service capabilities<\/strong>: Standardized options across environments improve consistency.<\/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>Read scaling<\/strong>: Add read-only nodes to increase read throughput without redesigning your application.<\/li>\n<li><strong>High availability patterns<\/strong>: Multi-node cluster setups reduce single points of failure.<\/li>\n<li><strong>Engine compatibility<\/strong>: Run familiar SQL engines (compatibility depends on selected PolarDB engine\/edition).<\/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><strong>Backups and restores<\/strong>: Built-in automated backup scheduling and restore workflows.<\/li>\n<li><strong>Observability integrations<\/strong>: Performance metrics and slow query analysis via Alibaba Cloud tooling (capability varies).<\/li>\n<li><strong>Lifecycle management<\/strong>: Console\/API-driven operations for scaling, maintenance, and configuration.<\/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><strong>Private networking<\/strong> with VPC and access controls via whitelists\/security groups.<\/li>\n<li><strong>Centralized identity<\/strong> via RAM with audit trails through ActionTrail.<\/li>\n<li><strong>Encryption options<\/strong> (in transit via SSL\/TLS; at rest depending on configuration and edition\u2014verify).<\/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><strong>Scale reads horizontally<\/strong> with read-only nodes.<\/li>\n<li><strong>Scale compute<\/strong> by changing node specifications (online resize options vary\u2014verify).<\/li>\n<li><strong>Storage growth<\/strong> is managed by the service (auto-scaling behavior depends on offering\u2014verify).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose PolarDB<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You need a managed relational database for <strong>OLTP<\/strong> workloads with:<\/li>\n<li>High availability requirements<\/li>\n<li>Read-heavy traffic patterns<\/li>\n<li>Managed backup\/restore<\/li>\n<li>Tight integration with Alibaba Cloud networking and IAM<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose PolarDB<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You need <strong>full OS-level control<\/strong> of the database host (use ECS + self-managed DB).<\/li>\n<li>You need a <strong>NoSQL<\/strong> model (consider Alibaba Cloud NoSQL offerings instead).<\/li>\n<li>You need a <strong>columnar analytics warehouse<\/strong> for large-scale OLAP (consider AnalyticDB or data warehouse services).<\/li>\n<li>You are locked into features of a specific community distribution or require custom database plugins not supported by the managed environment (verify engine constraints).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is PolarDB used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>E-commerce and retail (orders, inventory, carts)<\/li>\n<li>FinTech and payments (account ledgers, transaction metadata)<\/li>\n<li>Gaming (player profiles, sessions, leaderboards\u2014relational parts)<\/li>\n<li>Logistics and mobility (dispatching, tracking metadata)<\/li>\n<li>SaaS platforms (multi-tenant application databases)<\/li>\n<li>Media and content platforms (user accounts, subscriptions)<\/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 database provisioning<\/li>\n<li>DevOps\/SRE teams reducing operational toil<\/li>\n<li>Application teams needing reliable managed SQL without deep DBA investment<\/li>\n<li>Data engineers supporting operational data stores feeding downstream analytics<\/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 read scaling needs<\/li>\n<li>Microservices with per-service schemas (or shared schema with careful governance)<\/li>\n<li>Multi-tenant SaaS databases with strict isolation controls<\/li>\n<li>Hybrid architectures where operational data replicates to analytics systems<\/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>Classic three-tier apps (web\/app\/db)<\/li>\n<li>Microservices with a shared database or database-per-service (with governance)<\/li>\n<li>Event-driven architectures where writes land in PolarDB and events stream outward (streaming service selection varies)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production<\/strong>: HA cluster, multiple read-only nodes, strict network isolation, backup retention aligned with RPO\/RTO.<\/li>\n<li><strong>Dev\/Test<\/strong>: Smaller node specs, shorter backup retention, scheduled uptime, cost-optimized storage.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are practical PolarDB scenarios that align with managed relational databases on Alibaba Cloud.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Read-heavy e-commerce catalog<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Product pages generate heavy read traffic; writes are moderate.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Add read-only nodes and route read queries to read endpoints.<\/li>\n<li><strong>Example<\/strong>: A retail site uses primary for writes (price updates) and multiple read-only nodes for browsing and search filters.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) High-availability order processing database<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Orders must be persisted reliably; downtime is costly.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: HA cluster design and managed failover reduce downtime risk (verify failover behavior by edition\/engine).<\/li>\n<li><strong>Example<\/strong>: Checkout service writes orders to PolarDB and relies on automated failover during node faults.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) SaaS multi-tenant relational backend<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Need predictable provisioning and controlled access across tenants\/environments.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Standardized cluster provisioning, VPC isolation, RAM-based control plane access.<\/li>\n<li><strong>Example<\/strong>: A SaaS company creates separate clusters per environment and uses DMS workflows for controlled SQL changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Session store with SQL constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Sessions require relational integrity and joins (not a pure key\/value use case).<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Relational model + managed operations.<\/li>\n<li><strong>Example<\/strong>: A B2B portal stores authenticated sessions tied to accounts and roles.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) CMS and content metadata store<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Content management needs transactions and consistent reads.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Managed MySQL-compatible or PostgreSQL-compatible database with backups.<\/li>\n<li><strong>Example<\/strong>: A content platform stores article metadata, tags, and publishing workflows.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Regional application needing in-region low latency<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Users are concentrated in a region; cross-region DB latency is too high.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Region-scoped deployment close to compute in the same VPC.<\/li>\n<li><strong>Example<\/strong>: A China-region app runs ECS + PolarDB in the same region and VPC for low latency.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Reporting offload using read-only nodes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Reporting queries slow down transactional workloads.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Use read-only nodes for reporting queries; keep primary focused on writes.<\/li>\n<li><strong>Example<\/strong>: Business dashboards query read-only nodes during peak hours.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Migration from self-managed MySQL\/PostgreSQL<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Self-managed replication\/backups are fragile; upgrades are painful.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Managed service with familiar SQL compatibility and tooling.<\/li>\n<li><strong>Example<\/strong>: A team migrates an on-prem MySQL app to PolarDB and uses DMS to manage schema changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Microservices with shared relational database (governed)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Multiple services share a schema; need safe access and change control.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: DMS approvals, auditing, and controlled database accounts.<\/li>\n<li><strong>Example<\/strong>: A fintech uses DMS to enforce change workflows and limit privileged access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Burst traffic events (campaigns)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Flash sales create sudden read spikes.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Add read-only capacity (and possibly adjust specs) around events; remove later.<\/li>\n<li><strong>Example<\/strong>: Marketing campaign doubles traffic; read-only nodes absorb load.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Disaster recovery with cross-region replication (where supported)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Need a standby in another region for DR.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: Some PolarDB offerings support cross-region replication\/DR constructs (verify \u201cGlobal Database Network\u201d or equivalent in official docs).<\/li>\n<li><strong>Example<\/strong>: Primary runs in Region A; DR replica runs in Region B with defined RPO\/RTO.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Secure internal line-of-business apps<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Database must not be publicly exposed; strict access boundaries.<\/li>\n<li><strong>Why PolarDB fits<\/strong>: VPC-only access, private endpoints, whitelist controls, RAM control-plane permissions.<\/li>\n<li><strong>Example<\/strong>: HR application runs in a private VPC with PolarDB accessible only from specific ECS security groups.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Feature availability can differ by <strong>engine type<\/strong>, <strong>edition<\/strong>, and <strong>region<\/strong>. Always verify in the PolarDB official documentation for your selected engine\/edition.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Cluster-based managed database<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Lets you deploy a database as a cluster rather than a single instance.<\/li>\n<li><strong>Why it matters<\/strong>: Enables HA and scaling patterns not available in single-node deployments.<\/li>\n<li><strong>Practical benefit<\/strong>: Standardized endpoints and node management via console\/API.<\/li>\n<li><strong>Caveats<\/strong>: Node roles and endpoints vary by engine\/edition.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Primary + read-only node architecture (read scaling)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Supports adding read-only nodes to serve read traffic.<\/li>\n<li><strong>Why it matters<\/strong>: Read scaling is a common bottleneck for OLTP apps.<\/li>\n<li><strong>Practical benefit<\/strong>: Offload reporting and read-heavy queries.<\/li>\n<li><strong>Caveats<\/strong>: Replication lag can exist; apps must tolerate eventual consistency for reads (verify semantics).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Endpoints for simplified connectivity<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Provides stable connection endpoints for applications (for example cluster endpoints).<\/li>\n<li><strong>Why it matters<\/strong>: Reduces reconfiguration during failover or topology changes.<\/li>\n<li><strong>Practical benefit<\/strong>: Your app connects to an endpoint rather than targeting a specific node.<\/li>\n<li><strong>Caveats<\/strong>: Some endpoints may be read\/write vs read-only; ensure correct usage.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) High availability and failover<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Detects node failures and performs failover procedures.<\/li>\n<li><strong>Why it matters<\/strong>: Reduces downtime and manual intervention.<\/li>\n<li><strong>Practical benefit<\/strong>: Higher service uptime for production.<\/li>\n<li><strong>Caveats<\/strong>: RTO\/RPO depend on configuration and topology; verify SLA and failover behavior.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Automated backups and point-in-time recovery (PITR)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Automatically backs up data and supports restoring to a point in time.<\/li>\n<li><strong>Why it matters<\/strong>: Protects against accidental deletes, application bugs, and corruption.<\/li>\n<li><strong>Practical benefit<\/strong>: Faster recovery from logical failures than full rebuilds.<\/li>\n<li><strong>Caveats<\/strong>: Backup retention, restore time, and PITR granularity vary; backups cost money.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Manual snapshots \/ on-demand backups<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Lets you create backups before risky operations (schema changes, migrations).<\/li>\n<li><strong>Why it matters<\/strong>: Safer change management.<\/li>\n<li><strong>Practical benefit<\/strong>: Rollback option for deployment mistakes.<\/li>\n<li><strong>Caveats<\/strong>: Snapshot storage may incur extra charges.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Elastic scaling (compute and read capacity)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Resize node specs and\/or add\/remove read-only nodes (capabilities vary).<\/li>\n<li><strong>Why it matters<\/strong>: Align capacity with workload changes.<\/li>\n<li><strong>Practical benefit<\/strong>: Pay for what you need and scale as you grow.<\/li>\n<li><strong>Caveats<\/strong>: Some changes may involve brief disruption or maintenance windows\u2014verify.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Network isolation with VPC<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Runs in your VPC so traffic stays private.<\/li>\n<li><strong>Why it matters<\/strong>: Reduces exposure to the public internet.<\/li>\n<li><strong>Practical benefit<\/strong>: Better security posture and consistent latency.<\/li>\n<li><strong>Caveats<\/strong>: Cross-VPC access requires peering\/CEN and careful routing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Access control via accounts + RAM governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Database accounts control data-plane access; RAM controls control-plane actions.<\/li>\n<li><strong>Why it matters<\/strong>: Separate least-privilege access for people, apps, and automation.<\/li>\n<li><strong>Practical benefit<\/strong>: Reduce blast radius.<\/li>\n<li><strong>Caveats<\/strong>: Misconfigured privileges remain a major risk; enforce strong processes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Encryption in transit (SSL\/TLS)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Encrypts client-to-database connections.<\/li>\n<li><strong>Why it matters<\/strong>: Prevents credential and data exposure on the wire.<\/li>\n<li><strong>Practical benefit<\/strong>: Better compliance alignment.<\/li>\n<li><strong>Caveats<\/strong>: Client config must enable SSL; verify cipher support.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Encryption at rest (where supported)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Encrypts stored data using managed keys (often integrated with KMS).<\/li>\n<li><strong>Why it matters<\/strong>: Protects data if storage media is compromised.<\/li>\n<li><strong>Practical benefit<\/strong>: Compliance and risk reduction.<\/li>\n<li><strong>Caveats<\/strong>: Availability depends on engine\/edition; verify KMS requirements and key lifecycle responsibilities.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Maintenance and patching workflows<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Alibaba Cloud provides managed maintenance mechanisms (patching scope varies).<\/li>\n<li><strong>Why it matters<\/strong>: Reduces manual maintenance burden.<\/li>\n<li><strong>Practical benefit<\/strong>: More consistent security posture.<\/li>\n<li><strong>Caveats<\/strong>: Some upgrades may require downtime or compatibility checks; verify release notes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">13) Monitoring and performance diagnostics (CloudMonitor\/DAS)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Provides metrics and (optionally) deeper performance diagnostics.<\/li>\n<li><strong>Why it matters<\/strong>: You can detect slow queries, resource saturation, and replication lag early.<\/li>\n<li><strong>Practical benefit<\/strong>: Faster incident response and tuning.<\/li>\n<li><strong>Caveats<\/strong>: Advanced features may be extra-cost or limited by edition\u2014verify.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">14) Administrative tooling integration (DMS)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Allows controlled SQL execution, schema change workflows, and access approvals via DMS.<\/li>\n<li><strong>Why it matters<\/strong>: Reduces risky \u201cdirect-to-production\u201d database operations.<\/li>\n<li><strong>Practical benefit<\/strong>: Better governance and audit trails.<\/li>\n<li><strong>Caveats<\/strong>: Requires process adoption and permission design.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">15) Compatibility with common drivers and tools<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Works with standard JDBC\/ODBC and common clients for the selected engine compatibility.<\/li>\n<li><strong>Why it matters<\/strong>: Lower migration friction.<\/li>\n<li><strong>Practical benefit<\/strong>: Reuse existing application libraries and skills.<\/li>\n<li><strong>Caveats<\/strong>: Feature-level compatibility is not always 100%; validate critical SQL features and extensions.<\/li>\n<\/ul>\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 architecture<\/h3>\n\n\n\n<p>A typical PolarDB deployment places the cluster inside a VPC. Application services (often on ECS, ACK\/Kubernetes, or Function Compute depending on architecture) connect to PolarDB using private endpoints. PolarDB routes traffic to the correct compute node role (primary or read-only). Data persistence is handled by the managed storage layer.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control plane<\/strong>: Alibaba Cloud console\/API actions (create cluster, add nodes, configure backups) authenticated by <strong>RAM<\/strong>; actions recorded by <strong>ActionTrail<\/strong>.<\/li>\n<li><strong>Data plane<\/strong>: SQL traffic from clients to database endpoints over private VPC networking (optionally over SSL\/TLS).<\/li>\n<li><strong>Data path<\/strong>: Client \u2192 PolarDB endpoint \u2192 compute node \u2192 storage layer \u2192 response.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related Alibaba Cloud services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ECS<\/strong>: Run apps or bastion hosts for private connectivity.<\/li>\n<li><strong>VPC \/ Security Groups \/ NACLs<\/strong>: Network isolation and traffic control.<\/li>\n<li><strong>DMS<\/strong>: Central DBA tooling, approvals, auditing (where enabled).<\/li>\n<li><strong>CloudMonitor<\/strong>: Metrics and alerting (PolarDB publishes metrics; verify the metric set).<\/li>\n<li><strong>DAS<\/strong>: Performance insights and diagnostics (availability varies by edition\/engine).<\/li>\n<li><strong>ActionTrail<\/strong>: Records API actions for governance and auditing.<\/li>\n<li><strong>KMS<\/strong>: For encryption keys (when encryption at rest integrates with KMS\u2014verify).<\/li>\n<li><strong>DBS (Database Backup Service)<\/strong>: In some architectures, teams use DBS for unified backup policies across engines\/services (verify PolarDB support matrix).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>VPC networking and routing<\/li>\n<li>DNS (endpoint resolution)<\/li>\n<li>RAM for IAM<\/li>\n<li>Monitoring\/auditing services as optional dependencies<\/li>\n<\/ul>\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>Control plane<\/strong>: RAM users\/roles, policies, MFA, API keys.<\/li>\n<li><strong>Data plane<\/strong>: Database accounts (username\/password) and optional SSL\/TLS. Network access controls (VPC, whitelists) gate who can connect.<\/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 VPC access<\/strong> is the default\/desired pattern.<\/li>\n<li>Public endpoints may exist for some configurations, but are generally discouraged for production. Prefer private endpoints plus a bastion host\/VPN\/Direct Connect.<\/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>Enable metrics and alerts for CPU\/memory, connections, QPS, storage usage, replication lag (if exposed), and slow queries.<\/li>\n<li>Use ActionTrail for administrative changes auditing.<\/li>\n<li>Centralize operational logs from apps (not just DB metrics) to correlate incidents.<\/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  A[App on ECS\/ACK] --&gt;|SQL over VPC| E[PolarDB Endpoint]\n  E --&gt; P[Primary Node (Read\/Write)]\n  E --&gt; R[Read-only Node(s)]\n  P --&gt; S[(Managed Storage)]\n  R --&gt; S\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (example)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Internet\n    U[Users]\n  end\n\n  subgraph \"Alibaba Cloud VPC\"\n    direction TB\n\n    subgraph \"Public Subnet\"\n      ALB[ALB\/SLB\\n(HTTP\/HTTPS)]\n      NAT[NAT Gateway\\n(optional)]\n    end\n\n    subgraph \"Private App Subnets (Multi-Zone)\"\n      APP1[ECS\/ACK\\nApp Tier - Zone A]\n      APP2[ECS\/ACK\\nApp Tier - Zone B]\n      BAST[Bastion ECS\\n(SSH, restricted)]\n    end\n\n    subgraph \"Database Subnets\"\n      EP[PolarDB Endpoints]\n      PRI[Primary Node\\n(Read\/Write)]\n      RO1[Read-only Node\\nZone A]\n      RO2[Read-only Node\\nZone B]\n      ST[(PolarDB Storage Layer)]\n    end\n\n    APP1 --&gt;|SQL| EP\n    APP2 --&gt;|SQL| EP\n    BAST --&gt;|Admin SQL| EP\n\n    EP --&gt; PRI\n    EP --&gt; RO1\n    EP --&gt; RO2\n\n    PRI --&gt; ST\n    RO1 --&gt; ST\n    RO2 --&gt; ST\n\n    ALB --&gt; APP1\n    ALB --&gt; APP2\n  end\n\n  subgraph \"Ops \/ Governance\"\n    CM[CloudMonitor\\nAlerts]\n    DAS[DAS\\nDiagnostics (if enabled)]\n    DMS[DMS\\nDB Admin &amp; Change Control]\n    AT[ActionTrail\\nAudit]\n    KMS[KMS\\nKeys (if used)]\n  end\n\n  EP -.metrics.-&gt; CM\n  EP -.insights.-&gt; DAS\n  DMS -.admin.-&gt; EP\n  AT -.audit control plane.-&gt; EP\n  KMS -.encryption integration.-&gt; EP\n<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\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 active <strong>Alibaba Cloud account<\/strong>.<\/li>\n<li>A billing method configured (PolarDB is a paid service; free tier availability depends on promotions\u2014verify).<\/li>\n<li>Decide your purchasing model: <strong>pay-as-you-go<\/strong> or <strong>subscription<\/strong> (availability varies by region\/engine\u2014verify).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM (RAM)<\/h3>\n\n\n\n<p>You need RAM permissions to:\n&#8211; Create\/manage PolarDB clusters.\n&#8211; Create\/manage VPC, vSwitches, and ECS instances (for the lab client).\n&#8211; Manage security groups and network rules.\n&#8211; View billing and costs (optional but recommended).\n&#8211; Optional: manage KMS keys, ActionTrail, CloudMonitor alerts.<\/p>\n\n\n\n<p>If you are in an organization:\n&#8211; Use a <strong>RAM role<\/strong> for automation (CI\/CD) and a separate privileged admin role for infrastructure changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Tools needed<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Alibaba Cloud Console (web).<\/li>\n<li>Optional: <strong>Alibaba Cloud CLI<\/strong> (useful for automation). Verify current CLI commands\/modules for PolarDB in official docs:<\/li>\n<li>https:\/\/www.alibabacloud.com\/help\/en\/alibaba-cloud-cli\/latest\/what-is-alibaba-cloud-cli<\/li>\n<li>A SQL client:<\/li>\n<li><code>mysql<\/code> client for MySQL-compatible PolarDB<\/li>\n<li><code>psql<\/code> for PostgreSQL-compatible PolarDB<\/li>\n<li>DMS web SQL console (often easiest for quick tests)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PolarDB availability and engine offerings differ by region.<\/li>\n<li>Choose a region near your workload and with required features (multi-zone, encryption, etc.).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<p>Typical limits to be aware of (verify current quotas in console\/docs):\n&#8211; Number of clusters per account\/region.\n&#8211; Max read-only nodes per cluster.\n&#8211; Connection limits per node spec.\n&#8211; Backup retention limits and snapshot counts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (recommended for the lab)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>VPC<\/strong> with at least one vSwitch.<\/li>\n<li><strong>ECS<\/strong> instance in the same VPC to test private connectivity (or use DMS if you do not want ECS cost).<\/li>\n<li>Security group rules allowing outbound from ECS and inbound DB access only from ECS security group\/IP range.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<p>PolarDB pricing varies by:\n&#8211; <strong>Region<\/strong>\n&#8211; <strong>Engine compatibility (MySQL\/PostgreSQL\/etc.)<\/strong>\n&#8211; <strong>Edition and node specifications<\/strong>\n&#8211; <strong>Purchase model (subscription vs pay-as-you-go)<\/strong>\n&#8211; Optional features (backups retention, cross-region replication, monitoring add-ons, etc.)<\/p>\n\n\n\n<p>Always validate with official sources:\n&#8211; Product page: https:\/\/www.alibabacloud.com\/product\/polardb\n&#8211; Pricing page (region\/SKU specific; verify exact URL for your locale): https:\/\/www.alibabacloud.com\/product\/polardb\/pricing\n&#8211; Pricing calculator: https:\/\/www.alibabacloud.com\/pricing\/calculator<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Common pricing dimensions (typical model)<\/h3>\n\n\n\n<blockquote>\n<p>Exact line items differ by offering\u2014verify in your region\u2019s pricing page.<\/p>\n<\/blockquote>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Compute<\/strong>: billed per node (primary + read-only nodes) by instance class\/spec and time.<\/li>\n<li><strong>Storage<\/strong>: billed by provisioned\/used storage capacity and\/or performance tier (depending on offering).<\/li>\n<li><strong>Backups<\/strong>: backup storage beyond free quota (if any), longer retention, and cross-region backup features.<\/li>\n<li><strong>Network<\/strong>:<\/li>\n<li>Intra-VPC traffic is typically not billed like internet egress, but cross-zone or cross-region replication may have costs.<\/li>\n<li>Public internet egress (if you use public endpoints) can incur bandwidth charges.<\/li>\n<li><strong>Requests\/IOPS<\/strong>: some managed databases bill by I\/O or performance tier; verify if PolarDB in your selected offering bills I\/O separately.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<p>Alibaba Cloud sometimes offers trials or promotions. <strong>Do not assume a free tier<\/strong> for PolarDB; check current promotions and your account eligibility.<\/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>Number and size of compute nodes (especially read-only nodes you add for scaling).<\/li>\n<li>Storage usage and growth rate.<\/li>\n<li>Backup retention and snapshot frequency.<\/li>\n<li>Cross-region replication\/DR (if used).<\/li>\n<li>Leaving dev\/test clusters running 24\/7.<\/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 client\/bastion<\/strong> costs for private access and administration (if you don\u2019t use DMS only).<\/li>\n<li><strong>NAT Gateway<\/strong> costs if private subnets need outbound internet access for patching.<\/li>\n<li><strong>Monitoring add-ons<\/strong> (advanced diagnostics) if not included by default.<\/li>\n<li><strong>Data transfer<\/strong> if you replicate across regions or export large backups.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with <strong>minimal node specs<\/strong> that meet your CPU\/RAM needs and scale gradually.<\/li>\n<li>Prefer <strong>read-only nodes only when needed<\/strong>, and remove them after peak events.<\/li>\n<li>Set <strong>backup retention<\/strong> to the minimum that satisfies compliance and RPO\/RTO.<\/li>\n<li>Avoid public endpoints; keep traffic inside VPC to reduce risk and potential network charges.<\/li>\n<li>Use scheduling\/automation to shut down non-production environments if your organization allows (verify if PolarDB supports pausing\/stopping in your edition\u2014many managed DBs do not; if not supported, delete and recreate from snapshot for dev\/test).<\/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>Use this structure in the pricing calculator:\n&#8211; 1 PolarDB cluster\n&#8211; 1 primary node (smallest available spec in your region\/engine)\n&#8211; 0 read-only nodes (or 1 small read-only node if required by your HA policy)\n&#8211; Minimal initial storage\n&#8211; Standard backup retention (short, e.g., 7 days) and a single manual snapshot<\/p>\n\n\n\n<p>Then compare:\n&#8211; Pay-as-you-go hourly compute + storage\n&#8211; Subscription discounts (if you commit for months\/years)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>For a production workload, estimate:\n&#8211; Primary node sized for peak write throughput + memory working set.\n&#8211; 1\u2013N read-only nodes for read QPS and reporting.\n&#8211; Multi-zone deployment options (if separately priced).\n&#8211; Higher storage usage with growth buffers.\n&#8211; Longer backup retention (e.g., 30\u2013180 days) plus periodic manual snapshots.\n&#8211; DR: cross-region replication\/standby and associated network\/replication costs.\n&#8211; Operational tooling: DMS tiering (if applicable), DAS add-ons, log retention.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab uses <strong>PolarDB (MySQL-compatible)<\/strong> as the most common beginner path. If you choose PostgreSQL-compatible PolarDB, the flow is similar but client tooling and SQL syntax can differ slightly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Provision a PolarDB cluster in Alibaba Cloud, connect to it privately from an ECS instance in the same VPC, create a database and table, and validate read\/write connectivity.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Create (or reuse) a VPC and vSwitch.\n2. Provision a PolarDB cluster (MySQL-compatible) in that VPC.\n3. Create a database account and database.\n4. Launch a small ECS instance as a database client.\n5. Connect using the <code>mysql<\/code> client and run basic SQL.\n6. (Optional) Validate read-only endpoint if you add a read-only node.\n7. Clean up all resources to avoid ongoing charges.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Prepare networking (VPC and vSwitch)<\/h3>\n\n\n\n<p><strong>Console path (typical):<\/strong>\n&#8211; Alibaba Cloud Console \u2192 <strong>VPC<\/strong> \u2192 Create VPC\n&#8211; Create at least one <strong>vSwitch<\/strong> in a zone that supports PolarDB in your region.<\/p>\n\n\n\n<p><strong>Recommended settings<\/strong>\n&#8211; VPC CIDR: choose a non-overlapping RFC1918 range (e.g., <code>10.0.0.0\/16<\/code>)\n&#8211; vSwitch CIDR: a subset (e.g., <code>10.0.1.0\/24<\/code>)<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a VPC ID and vSwitch ID ready for PolarDB and ECS.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the VPC console, confirm the VPC and vSwitch status is <strong>Available<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create a PolarDB cluster (MySQL-compatible)<\/h3>\n\n\n\n<p><strong>Console path (typical):<\/strong>\n&#8211; Alibaba Cloud Console \u2192 <strong>PolarDB<\/strong> \u2192 Create Cluster<\/p>\n\n\n\n<p><strong>Key choices (verify names\/options in your console)<\/strong>\n&#8211; <strong>Billing<\/strong>: Pay-as-you-go (recommended for a short lab)\n&#8211; <strong>Region<\/strong>: choose a region close to you\n&#8211; <strong>Engine<\/strong>: PolarDB for MySQL (MySQL-compatible)\n&#8211; <strong>Edition\/Series<\/strong>: choose the most basic option that supports the lab (names vary\u2014verify)\n&#8211; <strong>Network<\/strong>: select the <strong>VPC<\/strong> and <strong>vSwitch<\/strong> from Step 1\n&#8211; <strong>Node spec<\/strong>: choose the smallest spec to reduce cost\n&#8211; <strong>Storage<\/strong>: keep defaults\/minimum where possible\n&#8211; <strong>High availability<\/strong>: keep default; if multi-zone is optional and increases cost, choose the minimum that meets your learning needs<\/p>\n\n\n\n<p>Create the cluster and wait until status is <strong>Running<\/strong>.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A PolarDB cluster is created with at least one node and one or more connection endpoints.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Open the cluster details page and confirm:\n  &#8211; Cluster status is <strong>Running<\/strong>\n  &#8211; You can see the <strong>endpoint(s)<\/strong> (addresses\/ports)\n  &#8211; The network type shows <strong>VPC<\/strong><\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Configure database accounts and create a database<\/h3>\n\n\n\n<p>In the PolarDB cluster console:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a <strong>privileged or standard account<\/strong> for administration.\n   &#8211; Use a strong password and store it securely.<\/li>\n<li>Create a <strong>database<\/strong> (schema) for the lab, for example: <code>labdb<\/code>.<\/li>\n<li>Grant the account permissions on <code>labdb<\/code>.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have credentials and a database ready.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the account list, confirm the account exists.\n&#8211; In the database list, confirm <code>labdb<\/code> exists and privileges are assigned.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Allow network access (whitelist\/security settings)<\/h3>\n\n\n\n<p>PolarDB typically uses a <strong>whitelist<\/strong> or access control list concept to permit client connections. The exact UI naming differs by product version\u2014verify in your cluster\u2019s \u201cSecurity\u201d or \u201cWhitelist\u201d section.<\/p>\n\n\n\n<p><strong>Secure lab approach<\/strong>\n&#8211; Only allow access from your ECS instance\u2019s private IP or the ECS security group CIDR.\n&#8211; Avoid <code>0.0.0.0\/0<\/code>.<\/p>\n\n\n\n<p><strong>What to do<\/strong>\n&#8211; Add the ECS client\u2019s private IP (you\u2019ll know it after Step 5), or temporarily add your vSwitch CIDR (e.g., <code>10.0.1.0\/24<\/code>) for the lab, then tighten later.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; PolarDB accepts connections only from approved private sources.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The whitelist shows your allowed IP(s)\/CIDR(s).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Create a small ECS instance as a private client<\/h3>\n\n\n\n<p><strong>Console path:<\/strong>\n&#8211; Alibaba Cloud Console \u2192 <strong>ECS<\/strong> \u2192 Create Instance<\/p>\n\n\n\n<p><strong>Recommended settings<\/strong>\n&#8211; Same <strong>Region<\/strong> and <strong>VPC\/vSwitch<\/strong> as PolarDB.\n&#8211; Small instance type.\n&#8211; OS: Alibaba Cloud Linux \/ CentOS \/ Ubuntu (any common Linux works).\n&#8211; Security group:\n  &#8211; Allow <strong>SSH (22)<\/strong> from your IP only.\n  &#8211; Outbound: allow to PolarDB (default outbound allow is common).<\/p>\n\n\n\n<p>After provisioning, SSH into the ECS instance.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can SSH to ECS, and ECS has a private IP in the same VPC as PolarDB.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Run:<\/p>\n\n\n\n<pre><code class=\"language-bash\">ip addr\n<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Note the private IP (e.g., <code>10.0.1.10<\/code>).<\/li>\n<\/ul>\n\n\n\n<p>Now return to <strong>Step 4<\/strong> and add this private IP to PolarDB\u2019s whitelist (if you didn\u2019t already).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Install the MySQL client on ECS<\/h3>\n\n\n\n<p>On the ECS instance, install a MySQL client.<\/p>\n\n\n\n<p><strong>Alibaba Cloud Linux \/ CentOS \/ RHEL-like:<\/strong><\/p>\n\n\n\n<pre><code class=\"language-bash\">sudo yum -y install mysql\n<\/code><\/pre>\n\n\n\n<p><strong>Ubuntu\/Debian-like:<\/strong><\/p>\n\n\n\n<pre><code class=\"language-bash\">sudo apt-get update\nsudo apt-get -y install mysql-client\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The <code>mysql<\/code> command is 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 7: Connect to PolarDB and run SQL<\/h3>\n\n\n\n<p>From the PolarDB cluster details page, copy the <strong>VPC endpoint<\/strong> and port (commonly <code>3306<\/code> for MySQL-compatible engines; verify your endpoint details).<\/p>\n\n\n\n<p>Connect:<\/p>\n\n\n\n<pre><code class=\"language-bash\">mysql -h &lt;POLARDB_ENDPOINT&gt; -P 3306 -u &lt;DB_USERNAME&gt; -p\n<\/code><\/pre>\n\n\n\n<p>Then in the MySQL shell:<\/p>\n\n\n\n<pre><code class=\"language-sql\">SHOW DATABASES;\nUSE labdb;\n\nCREATE TABLE IF NOT EXISTS messages (\n  id BIGINT PRIMARY KEY AUTO_INCREMENT,\n  message VARCHAR(255) NOT NULL,\n  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP\n);\n\nINSERT INTO messages (message) VALUES\n('hello from ecs client'),\n('polardb lab insert');\n\nSELECT * FROM messages;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can connect over VPC, create a table, insert rows, and query them.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The <code>SELECT<\/code> returns at least 2 rows.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 8 (Optional): Validate read scaling with a read-only node and endpoint<\/h3>\n\n\n\n<p>If your PolarDB offering supports adding read-only nodes:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Add a <strong>read-only node<\/strong> in the cluster console.<\/li>\n<li>Identify the <strong>read-only endpoint<\/strong> (or configure an endpoint suitable for reads\u2014naming varies by engine\/edition).<\/li>\n<\/ol>\n\n\n\n<p>Connect to the read-only endpoint and verify you can read:<\/p>\n\n\n\n<pre><code class=\"language-bash\">mysql -h &lt;READONLY_ENDPOINT&gt; -P 3306 -u &lt;DB_USERNAME&gt; -p -e \"USE labdb; SELECT COUNT(*) FROM messages;\"\n<\/code><\/pre>\n\n\n\n<p>Then verify that writes are blocked (expected failure) if it is strictly read-only:<\/p>\n\n\n\n<pre><code class=\"language-bash\">mysql -h &lt;READONLY_ENDPOINT&gt; -P 3306 -u &lt;DB_USERNAME&gt; -p -e \"USE labdb; INSERT INTO messages(message) VALUES ('should fail on read-only');\"\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Reads succeed from the read endpoint.\n&#8211; Writes fail or are routed depending on endpoint semantics (verify your endpoint behavior in official docs).<\/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 checklist:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>[ ] PolarDB cluster status is <strong>Running<\/strong><\/li>\n<li>[ ] ECS can reach the endpoint (VPC)<\/li>\n<li>[ ] Database user can authenticate<\/li>\n<li>[ ] SQL operations succeed on the primary\/read-write endpoint<\/li>\n<li>[ ] (Optional) Read-only endpoint serves reads as expected<\/li>\n<\/ul>\n\n\n\n<p><strong>Quick connectivity test (TCP)<\/strong>\nIf <code>nc<\/code> is available:<\/p>\n\n\n\n<pre><code class=\"language-bash\">nc -vz &lt;POLARDB_ENDPOINT&gt; 3306\n<\/code><\/pre>\n\n\n\n<p>If not, you can install netcat or rely on <code>mysql<\/code> connection attempts.<\/p>\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><strong>Issue: \u201cAccess denied for user\u201d<\/strong>\n&#8211; Confirm username\/password.\n&#8211; Verify the user has privileges on <code>labdb<\/code>.\n&#8211; If using DMS-created accounts vs console-created accounts, re-check which credentials you used.<\/p>\n\n\n\n<p><strong>Issue: Connection timeout<\/strong>\n&#8211; Verify PolarDB is in the <strong>same VPC<\/strong> as ECS.\n&#8211; Ensure the PolarDB whitelist includes the ECS private IP (or the correct CIDR).\n&#8211; Check ECS security group outbound rules (and any NACLs).<\/p>\n\n\n\n<p><strong>Issue: \u201cUnknown host\u201d<\/strong>\n&#8211; Ensure endpoint is copied correctly.\n&#8211; Confirm ECS DNS resolution (try <code>nslookup &lt;endpoint&gt;<\/code> if tools are available).<\/p>\n\n\n\n<p><strong>Issue: Writes fail on endpoint<\/strong>\n&#8211; You may be connected to a <strong>read-only endpoint<\/strong>.\n&#8211; Use the cluster\u2019s <strong>read\/write endpoint<\/strong> (names vary\u2014verify in console).<\/p>\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 a safe order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Delete the ECS instance<\/strong>\n   &#8211; ECS Console \u2192 Instances \u2192 Release (ensure disks and EIP are also released if applicable).<\/li>\n<li><strong>Delete the PolarDB cluster<\/strong>\n   &#8211; PolarDB Console \u2192 Cluster \u2192 Delete\/Release\n   &#8211; Review snapshot\/backup retention prompts; deleting snapshots may be required to stop storage charges.<\/li>\n<li><strong>(Optional) Remove VPC resources<\/strong>\n   &#8211; Delete unused vSwitches and VPC if created only for this lab.<\/li>\n<\/ol>\n\n\n\n<p>Confirm in Billing\/Cost Center that no active billable resources remain.<\/p>\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>Use <strong>private VPC connectivity<\/strong> for applications; avoid public endpoints for production.<\/li>\n<li>Separate <strong>read and write traffic<\/strong>:<\/li>\n<li>Write-heavy services use the read\/write endpoint.<\/li>\n<li>Read-heavy services and reporting use read-only endpoints\/nodes (if supported).<\/li>\n<li>Design for <strong>failure<\/strong>:<\/li>\n<li>Use endpoints rather than node-specific addresses.<\/li>\n<li>Ensure application retry logic and connection pool behavior are compatible with failover.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>RAM roles<\/strong> for automation; avoid long-lived AccessKey secrets in CI.<\/li>\n<li>Enforce <strong>MFA<\/strong> for privileged RAM users.<\/li>\n<li>Apply least privilege: separate roles for networking, database provisioning, and billing access.<\/li>\n<li>Restrict who can modify <strong>whitelists<\/strong>, endpoints, and backup settings.<\/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>Start small; scale based on measured metrics (CPU, connections, QPS, latency).<\/li>\n<li>Avoid over-provisioning read-only nodes \u201cjust in case\u201d.<\/li>\n<li>Tune backup retention to business requirements.<\/li>\n<li>Regularly delete unused snapshots and old dev\/test clusters.<\/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>Use connection pooling; keep connection counts within node limits.<\/li>\n<li>Create the right indexes; avoid unbounded queries.<\/li>\n<li>Use slow query logs and performance insights (DAS\/engine tools) to find hotspots.<\/li>\n<li>Keep transactions short; avoid long-running locks.<\/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>Set clear <strong>RPO\/RTO<\/strong> targets and align with backup and DR features.<\/li>\n<li>Regularly test restore procedures (PITR and snapshot restore).<\/li>\n<li>Avoid single-client dependency: run application tiers across multiple zones.<\/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>Use DMS (or controlled processes) for schema migrations and production SQL execution.<\/li>\n<li>Set alarms for:<\/li>\n<li>CPU\/memory saturation<\/li>\n<li>Storage growth<\/li>\n<li>Connections nearing limits<\/li>\n<li>Slow query spikes<\/li>\n<li>Replication lag (if exposed)<\/li>\n<li>Maintain runbooks for:<\/li>\n<li>Failover events<\/li>\n<li>Restore workflows<\/li>\n<li>Scaling procedures<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use consistent naming: <code>env-app-region-db<\/code> patterns (e.g., <code>prod-checkout-cn-hz-polardb<\/code>).<\/li>\n<li>Tag resources with <code>Environment<\/code>, <code>Owner<\/code>, <code>CostCenter<\/code>, <code>DataClass<\/code> (if your org uses data classification).<\/li>\n<li>Document:<\/li>\n<li>Endpoint usage (which app uses which endpoint)<\/li>\n<li>Backup retention policy and restore steps<\/li>\n<li>Change windows and maintenance preferences<\/li>\n<\/ul>\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>Control plane<\/strong>: RAM policies determine who can create\/modify\/delete PolarDB clusters, change network settings, or view credentials.<\/li>\n<li><strong>Data plane<\/strong>: Database users and privileges determine who can run SQL and access schemas\/tables.<\/li>\n<\/ul>\n\n\n\n<p>Recommendations:\n&#8211; Do not share a single \u201cadmin\u201d database account across teams.\n&#8211; Create separate accounts for apps with least-privilege grants (e.g., read-only vs read\/write).\n&#8211; Rotate credentials and prefer secrets management patterns (store in a secure vault; Alibaba Cloud has secret management options\u2014verify current product availability in your region).<\/p>\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>: Enable SSL\/TLS for database connections when supported; update clients to enforce TLS.<\/li>\n<li><strong>At rest<\/strong>: Use encryption at rest when available for your engine\/edition; validate KMS integration and key policies.<\/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<\/strong> access.<\/li>\n<li>Avoid public endpoints; if unavoidable:<\/li>\n<li>Restrict by IP allowlist to known corporate egress IPs<\/li>\n<li>Enforce TLS<\/li>\n<li>Use bastion\/VPN\/Direct Connect instead where possible<\/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 hardcode DB passwords in code repositories.<\/li>\n<li>Use environment variables only if your runtime is locked down; prefer a secret manager.<\/li>\n<li>Implement credential rotation and deploy pipelines that can update secrets safely.<\/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 <strong>ActionTrail<\/strong> for control-plane audit trails.<\/li>\n<li>Use DMS approvals\/auditing for production SQL operations (where feasible).<\/li>\n<li>Retain logs according to compliance requirements.<\/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>Data residency: deploy in regions appropriate for your regulatory needs.<\/li>\n<li>Access controls: implement segregation of duties (SoD) between infra admins and app operators.<\/li>\n<li>Retention: align backup retention with policy (and ensure secure deletion).<\/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>Whitelisting <code>0.0.0.0\/0<\/code> for convenience.<\/li>\n<li>Using a single privileged DB user for all applications.<\/li>\n<li>Disabling TLS while allowing cross-network access.<\/li>\n<li>No monitoring on connection spikes (can indicate brute-force attempts if publicly reachable).<\/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>Use private VPC endpoints and restrict inbound to application subnets\/security groups.<\/li>\n<li>Enforce RAM least privilege; require MFA for sensitive operations.<\/li>\n<li>Enable backup encryption and at-rest encryption where available.<\/li>\n<li>Build a restore drill into your quarterly\/biannual operational process.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Because PolarDB has multiple engines\/editions and regional differences, treat these as common \u201ccheck-before-you-build\u201d items:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Feature availability varies<\/strong> by engine\/edition\/region (encryption, cross-region replication, serverless options, endpoint types).<\/li>\n<li><strong>Compatibility is not always identical<\/strong> to community MySQL\/PostgreSQL\/Oracle features; validate:<\/li>\n<li>SQL modes<\/li>\n<li>Stored procedures\/triggers<\/li>\n<li>Extensions<\/li>\n<li>Character sets\/collations<\/li>\n<li>Replication semantics and lag behavior<\/li>\n<li><strong>Replication lag<\/strong> can affect read-only query correctness for time-sensitive reads.<\/li>\n<li><strong>Connection limits<\/strong> depend on node specs; connection storms during deployments can trigger failures.<\/li>\n<li><strong>Backup costs<\/strong> can grow significantly with high churn databases and long retention.<\/li>\n<li><strong>Cross-zone\/cross-region architectures<\/strong> can introduce extra costs and latency.<\/li>\n<li><strong>Maintenance windows<\/strong>: some operations (upgrades\/resizes) can cause brief disruptions; plan changes carefully.<\/li>\n<li><strong>Migration challenges<\/strong>:<\/li>\n<li>Large datasets require careful cutover planning<\/li>\n<li>Application connection strings\/endpoints must be managed<\/li>\n<li>Charset\/collation differences can break comparisons\/sorts<\/li>\n<li><strong>Public endpoint risk<\/strong>: Misconfiguration can expose your DB to the internet.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>PolarDB is one option in Alibaba Cloud Databases and beyond. Here\u2019s how it typically compares.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key alternatives<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Alibaba Cloud ApsaraDB RDS<\/strong>: Managed single-instance (with HA options) relational databases.<\/li>\n<li><strong>PolarDB-X<\/strong>: A separate product oriented toward distributed scale-out relational patterns (do not confuse with PolarDB).<\/li>\n<li><strong>Self-managed MySQL\/PostgreSQL on ECS<\/strong>: Maximum control but highest operational burden.<\/li>\n<li><strong>AWS Aurora \/ Azure Database \/ Google AlloyDB<\/strong>: Comparable managed relational services in other clouds.<\/li>\n<\/ul>\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>Alibaba Cloud PolarDB<\/strong><\/td>\n<td>Managed relational clusters needing HA + read scaling<\/td>\n<td>Cluster endpoints, read-only scaling, managed backups, strong Alibaba Cloud VPC integration<\/td>\n<td>Feature differences by edition\/engine; costs can increase with nodes\/backups<\/td>\n<td>You want managed HA + scaling in Alibaba Cloud with familiar SQL<\/td>\n<\/tr>\n<tr>\n<td><strong>Alibaba Cloud ApsaraDB RDS<\/strong><\/td>\n<td>Straightforward managed relational DB needs<\/td>\n<td>Simpler model, broad engine support, widely used<\/td>\n<td>May offer less cluster-style read scaling depending on engine\/architecture<\/td>\n<td>You need a simpler managed DB and don\u2019t need PolarDB\u2019s cluster model<\/td>\n<\/tr>\n<tr>\n<td><strong>Alibaba Cloud PolarDB-X<\/strong><\/td>\n<td>Scale-out distributed SQL patterns<\/td>\n<td>Horizontal sharding\/distribution features (product-specific)<\/td>\n<td>Different operational model and compatibility considerations<\/td>\n<td>You need distributed scale-out beyond read replicas (verify suitability)<\/td>\n<\/tr>\n<tr>\n<td><strong>Self-managed DB on ECS<\/strong><\/td>\n<td>Full control and custom setups<\/td>\n<td>Full OS\/db control, custom extensions<\/td>\n<td>Highest ops burden: HA, backups, patching, monitoring<\/td>\n<td>You need custom DB features or strict control not available in managed DBaaS<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS Aurora<\/strong><\/td>\n<td>Managed relational on AWS<\/td>\n<td>Similar managed cluster goals<\/td>\n<td>Different cloud ecosystem and networking\/IAM<\/td>\n<td>You are standardized on AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Google AlloyDB<\/strong><\/td>\n<td>PostgreSQL-oriented managed performance on GCP<\/td>\n<td>Managed Postgres with performance focus<\/td>\n<td>Different ecosystem; migration cost<\/td>\n<td>You are standardized on GCP and need managed Postgres<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Database for MySQL\/PostgreSQL<\/strong><\/td>\n<td>Managed SQL on Azure<\/td>\n<td>Integration with Azure identity and tooling<\/td>\n<td>Different ecosystem<\/td>\n<td>You are standardized on Azure<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\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: Multi-service e-commerce platform<\/h3>\n\n\n\n<p><strong>Problem<\/strong>\nAn enterprise e-commerce company runs dozens of microservices. The product catalog and inventory services face high read traffic, and reporting queries sometimes degrade checkout performance. The company also needs strict network isolation and audited operational access.<\/p>\n\n\n\n<p><strong>Proposed architecture<\/strong>\n&#8211; VPC with separate subnets for app and database.\n&#8211; ECS\/ACK for microservices across multiple zones.\n&#8211; PolarDB cluster for transactional data:\n  &#8211; Primary node for writes\n  &#8211; Multiple read-only nodes for catalog reads and reporting\n&#8211; DMS for controlled SQL changes and audited access.\n&#8211; CloudMonitor + DAS (if supported) for performance monitoring and alerting.\n&#8211; ActionTrail for auditing administrative changes.<\/p>\n\n\n\n<p><strong>Why PolarDB was chosen<\/strong>\n&#8211; Managed cluster operations reduce DBA overhead.\n&#8211; Read-only scaling supports high read QPS without overloading the primary.\n&#8211; VPC-only connectivity aligns with security requirements.<\/p>\n\n\n\n<p><strong>Expected outcomes<\/strong>\n&#8211; Improved read performance and reduced impact of reporting queries.\n&#8211; Faster recovery from node failures (failover procedures managed by service).\n&#8211; Better governance through audited change workflows.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: SaaS application backend<\/h3>\n\n\n\n<p><strong>Problem<\/strong>\nA startup runs a multi-tenant SaaS product. The team is small, with limited DBA experience. They need reliable backups and the ability to scale reads as usage grows, without maintaining replication and failover manually.<\/p>\n\n\n\n<p><strong>Proposed architecture<\/strong>\n&#8211; One VPC, private subnets.\n&#8211; ECS for app tier (or containers).\n&#8211; One PolarDB cluster (MySQL-compatible) for primary application data.\n&#8211; Daily automated backups, short retention in dev, longer in prod.\n&#8211; DMS for safe production queries and account control.<\/p>\n\n\n\n<p><strong>Why PolarDB was chosen<\/strong>\n&#8211; Familiar MySQL-compatible development experience.\n&#8211; Managed backups and simplified scaling.\n&#8211; Clear path to add read-only capacity as customers grow.<\/p>\n\n\n\n<p><strong>Expected outcomes<\/strong>\n&#8211; Reduced operational load and fewer late-night incidents.\n&#8211; Ability to grow from one node to a small cluster without redesign.\n&#8211; Better customer trust due to consistent availability and recoverability.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<p>1) <strong>Is PolarDB the same as ApsaraDB RDS?<\/strong><br\/>\nNo. Both are Alibaba Cloud managed relational services, but <strong>PolarDB<\/strong> is cluster-oriented with its own architecture and scaling model. Choose based on your workload needs and feature availability.<\/p>\n\n\n\n<p>2) <strong>Is PolarDB the same as PolarDB-X?<\/strong><br\/>\nNo. <strong>PolarDB-X<\/strong> is a separate product with a different scope (distributed scale-out patterns). This tutorial is only about <strong>PolarDB<\/strong>.<\/p>\n\n\n\n<p>3) <strong>Which engines does PolarDB support?<\/strong><br\/>\nPolarDB provides engine compatibility options (commonly MySQL-compatible and PostgreSQL-compatible; additional options may exist). <strong>Verify the supported engines and versions in official docs for your region.<\/strong><\/p>\n\n\n\n<p>4) <strong>Can I run PolarDB in my own VPC?<\/strong><br\/>\nYes\u2014PolarDB is typically deployed into a selected <strong>VPC and vSwitch<\/strong> for private connectivity.<\/p>\n\n\n\n<p>5) <strong>Can PolarDB be publicly accessible?<\/strong><br\/>\nSome configurations may provide public connectivity options, but for production security you should prefer <strong>VPC-only<\/strong> access and connect via VPN\/Direct Connect\/bastion if remote access is needed.<\/p>\n\n\n\n<p>6) <strong>How do I scale reads?<\/strong><br\/>\nAdd <strong>read-only nodes<\/strong> and route read traffic to the appropriate endpoint(s). Application-level read\/write splitting may be required.<\/p>\n\n\n\n<p>7) <strong>Does PolarDB guarantee zero replication lag?<\/strong><br\/>\nNo. Like most systems with read replicas, lag can occur. If your app requires read-after-write consistency, read from the primary\/read-write endpoint.<\/p>\n\n\n\n<p>8) <strong>How do backups work?<\/strong><br\/>\nPolarDB typically supports automated backups and restore workflows (including point-in-time recovery). Retention and restore options vary\u2014verify in the docs and console for your engine\/edition.<\/p>\n\n\n\n<p>9) <strong>Can I restore to a new cluster?<\/strong><br\/>\nCommonly, managed database services support restoring from backups\/snapshots into a new cluster. Verify the exact restore workflow and limitations for your offering.<\/p>\n\n\n\n<p>10) <strong>How do I monitor PolarDB?<\/strong><br\/>\nUse Alibaba Cloud monitoring tools such as <strong>CloudMonitor<\/strong> and (where supported) <strong>DAS<\/strong> for deeper diagnostics. Also monitor application-level metrics (latency, error rate).<\/p>\n\n\n\n<p>11) <strong>How do I manage schema changes safely?<\/strong><br\/>\nUse <strong>DMS<\/strong> workflows, backups before changes, migration tooling, and staged rollouts. Avoid manual changes on production without approvals and rollback plans.<\/p>\n\n\n\n<p>12) <strong>Does PolarDB support encryption at rest?<\/strong><br\/>\nOften yes, but <strong>availability depends on engine\/edition\/region<\/strong>. Verify in official docs and confirm KMS requirements if applicable.<\/p>\n\n\n\n<p>13) <strong>What is the recommended way to connect from my laptop?<\/strong><br\/>\nDo not expose the database publicly. Use a <strong>bastion ECS<\/strong>, VPN, or Direct Connect into the VPC, or use DMS web SQL console for controlled access.<\/p>\n\n\n\n<p>14) <strong>How do I reduce cost in dev\/test?<\/strong><br\/>\nUse the smallest node specs, minimal retention, and delete clusters when not needed. Avoid adding read-only nodes unless you are explicitly testing scaling.<\/p>\n\n\n\n<p>15) <strong>What should I do before migrating production to PolarDB?<\/strong><br\/>\nRun a proof of concept:\n&#8211; Validate SQL compatibility and performance\n&#8211; Measure latency from your app tier\n&#8211; Test backup\/restore and failover behavior\n&#8211; Plan cutover and rollback<\/p>\n\n\n\n<p>16) <strong>Can I use PolarDB for analytics workloads?<\/strong><br\/>\nPolarDB is primarily for relational transactional workloads. For heavy analytics, consider Alibaba Cloud analytics databases\/warehouses. You can also offload reads to read-only nodes for light reporting.<\/p>\n\n\n\n<p>17) <strong>How do I handle connection storms during deployments?<\/strong><br\/>\nUse connection pooling, exponential backoff retries, and limit concurrency during rolling deploys. Ensure your node specs and connection limits match expected peak connections.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn PolarDB<\/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 Documentation<\/td>\n<td>PolarDB Documentation (Alibaba Cloud Help Center) \u2014 https:\/\/www.alibabacloud.com\/help\/en\/polardb\/<\/td>\n<td>Primary source for current features, engine support, APIs, and operational guides<\/td>\n<\/tr>\n<tr>\n<td>Official Product Page<\/td>\n<td>PolarDB Product Page \u2014 https:\/\/www.alibabacloud.com\/product\/polardb<\/td>\n<td>High-level overview, supported editions, links to docs and updates<\/td>\n<\/tr>\n<tr>\n<td>Official Pricing<\/td>\n<td>PolarDB Pricing \u2014 https:\/\/www.alibabacloud.com\/product\/polardb\/pricing<\/td>\n<td>Region\/SKU-based pricing model and billing dimensions (verify region)<\/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 for your region, node size, and storage\/backup needs<\/td>\n<\/tr>\n<tr>\n<td>Getting Started (Official)<\/td>\n<td>PolarDB Getting Started (within docs) \u2014 https:\/\/www.alibabacloud.com\/help\/en\/polardb\/<\/td>\n<td>Step-by-step provisioning and connection guidance (verify the exact \u201cQuick Start\u201d page inside docs)<\/td>\n<\/tr>\n<tr>\n<td>Admin Tooling<\/td>\n<td>Data Management (DMS) \u2014 https:\/\/www.alibabacloud.com\/product\/dms<\/td>\n<td>Safe SQL execution, schema change workflows, access control and auditing patterns<\/td>\n<\/tr>\n<tr>\n<td>Monitoring\/Diagnostics<\/td>\n<td>Database Autonomy Service (DAS) \u2014 https:\/\/www.alibabacloud.com\/product\/das<\/td>\n<td>Performance diagnostics and tuning insights (feature availability varies)<\/td>\n<\/tr>\n<tr>\n<td>Auditing<\/td>\n<td>ActionTrail \u2014 https:\/\/www.alibabacloud.com\/product\/actiontrail<\/td>\n<td>Track API actions for governance and compliance<\/td>\n<\/tr>\n<tr>\n<td>Networking<\/td>\n<td>VPC Documentation \u2014 https:\/\/www.alibabacloud.com\/help\/en\/vpc\/<\/td>\n<td>Required for secure private deployments and routing design<\/td>\n<\/tr>\n<tr>\n<td>Compute Client<\/td>\n<td>ECS Documentation \u2014 https:\/\/www.alibabacloud.com\/help\/en\/ecs\/<\/td>\n<td>Run private clients\/bastions and application tiers that connect to PolarDB<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\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, CI\/CD, DevOps practices around cloud services (verify PolarDB-specific coverage on site)<\/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 DevOps learners<\/td>\n<td>SCM, DevOps 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, monitoring, reliability practices<\/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, observability, incident management<\/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 teams exploring AIOps<\/td>\n<td>AIOps concepts, monitoring automation<\/td>\n<td>check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\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>DevOps\/cloud training content (verify current offerings)<\/td>\n<td>Beginners to intermediate engineers<\/td>\n<td>https:\/\/www.rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training and mentoring (verify service catalog)<\/td>\n<td>DevOps practitioners<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps consulting\/training listings (verify offerings)<\/td>\n<td>Teams needing short-term help<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support and guidance (verify scope)<\/td>\n<td>Ops\/DevOps teams<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\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 exact catalog)<\/td>\n<td>Architecture, migrations, operations<\/td>\n<td>PolarDB migration planning, VPC design, monitoring setup<\/td>\n<td>https:\/\/www.cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps and cloud consulting\/training<\/td>\n<td>DevOps transformation, automation<\/td>\n<td>CI\/CD for DB changes, infrastructure-as-code patterns around Alibaba Cloud<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting services (verify service list)<\/td>\n<td>Reliability, automation, cloud operations<\/td>\n<td>Production readiness reviews, cost optimization, observability<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\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 PolarDB<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SQL fundamentals: schema design, indexing, transactions, isolation levels.<\/li>\n<li>Basics of relational performance: query plans, slow queries, connection pooling.<\/li>\n<li>Alibaba Cloud fundamentals:<\/li>\n<li>VPC, vSwitch, routing, security groups<\/li>\n<li>ECS basics<\/li>\n<li>RAM (users, roles, policies)<\/li>\n<li>Basic Linux administration for client hosts and troubleshooting.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after PolarDB<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Advanced database operations:<\/li>\n<li>Backup\/restore drills<\/li>\n<li>Capacity planning and performance testing<\/li>\n<li>Schema migration strategies (online migrations, backward-compatible changes)<\/li>\n<li>Observability:<\/li>\n<li>CloudMonitor alerting<\/li>\n<li>DAS (if used) and query optimization workflows<\/li>\n<li>Security:<\/li>\n<li>TLS enforcement, secrets management, audit trails<\/li>\n<li>Network segmentation and bastion\/VPN patterns<\/li>\n<li>DR architectures:<\/li>\n<li>Cross-region strategies (where supported)<\/li>\n<li>Application-level resilience and failover 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 Engineer \/ Cloud Architect (designing managed database solutions)<\/li>\n<li>DevOps Engineer \/ Platform Engineer (provisioning automation, governance)<\/li>\n<li>SRE (reliability, monitoring, incident response)<\/li>\n<li>Database Engineer \/ DBA (performance tuning, migrations, governance)<\/li>\n<li>Backend Engineer (schema design, query optimization, scaling reads)<\/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 programs change over time. If you are targeting certification:\n&#8211; Start with Alibaba Cloud foundational certifications (cloud fundamentals).\n&#8211; Move to associate\/professional tracks that include networking, security, and databases.<br\/>\n<strong>Verify current Alibaba Cloud certification paths on the official certification site.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Build a three-tier app (ECS\/ACK + PolarDB) with read\/write split.<\/li>\n<li>Implement automated schema migrations with rollback strategy (use DMS + CI pipeline).<\/li>\n<li>Simulate a traffic spike and scale read-only nodes; measure latency\/QPS changes.<\/li>\n<li>Perform PITR restore into a new cluster and validate data correctness.<\/li>\n<li>Implement least-privilege DB accounts and demonstrate blocked operations.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ACK<\/strong>: Alibaba Cloud Container Service for Kubernetes.<\/li>\n<li><strong>ActionTrail<\/strong>: Alibaba Cloud service that records API calls for auditing.<\/li>\n<li><strong>ALB\/SLB<\/strong>: Load balancing services for application traffic (not for database SQL traffic).<\/li>\n<li><strong>Backup retention<\/strong>: How long backups are kept before deletion.<\/li>\n<li><strong>Cluster endpoint<\/strong>: A stable connection address representing the cluster (exact semantics vary).<\/li>\n<li><strong>DAS (Database Autonomy Service)<\/strong>: Diagnostics and performance insights service (availability varies).<\/li>\n<li><strong>DMS (Data Management)<\/strong>: Web-based database management and governance tool.<\/li>\n<li><strong>ECS (Elastic Compute Service)<\/strong>: Alibaba Cloud virtual machine service.<\/li>\n<li><strong>Failover<\/strong>: Switching database role\/service to another node when a failure occurs.<\/li>\n<li><strong>PITR (Point-in-Time Recovery)<\/strong>: Restoring a database to a specific time within a retention window.<\/li>\n<li><strong>Primary node<\/strong>: The node that handles writes (read\/write).<\/li>\n<li><strong>RAM (Resource Access Management)<\/strong>: Alibaba Cloud IAM service.<\/li>\n<li><strong>Read-only node<\/strong>: A node used to serve read queries and scale read capacity.<\/li>\n<li><strong>RPO\/RTO<\/strong>: Recovery Point Objective \/ Recovery Time Objective.<\/li>\n<li><strong>Security group<\/strong>: Virtual firewall for ECS and some other resources.<\/li>\n<li><strong>vSwitch<\/strong>: Subnet inside a VPC.<\/li>\n<li><strong>VPC (Virtual Private Cloud)<\/strong>: Private networking boundary in Alibaba Cloud.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>PolarDB is Alibaba Cloud\u2019s managed relational database cluster service in the <strong>Databases<\/strong> category, designed for high availability, operational simplicity, and read scaling through cluster architecture and managed features like backups and endpoints.<\/p>\n\n\n\n<p>It matters because it helps teams deliver reliable SQL-backed applications faster, with fewer operational burdens than self-managed databases\u2014especially when you need high availability and a clear path to scale reads.<\/p>\n\n\n\n<p>From a cost and security perspective:\n&#8211; Costs are driven mainly by <strong>node specs<\/strong>, <strong>number of nodes<\/strong>, <strong>storage growth<\/strong>, and <strong>backup retention<\/strong>\u2014use the official pricing page and calculator for accurate estimates.\n&#8211; Secure deployments should prioritize <strong>VPC-only access<\/strong>, least-privilege <strong>RAM<\/strong> and database accounts, <strong>TLS<\/strong>, and audited operations (ActionTrail\/DMS).<\/p>\n\n\n\n<p>Use PolarDB when you want a managed relational database cluster on Alibaba Cloud with scalable reads and built-in operational features. If you need full host control or non-relational models, consider alternatives.<\/p>\n\n\n\n<p>Next step: follow the official PolarDB documentation for your chosen engine\/edition, then extend the lab by adding read-only nodes, enabling monitoring alerts, and practicing backup\/restore drills in a staging environment.<\/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-71","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\/71","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=71"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/71\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=71"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=71"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=71"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}