{"id":328,"date":"2026-08-05T10:50:03","date_gmt":"2026-08-05T10:50:03","guid":{"rendered":""},"modified":"2026-08-05T10:50:03","modified_gmt":"2026-08-05T10:50:03","slug":"oracle-database-migration-alternatives_-a-tco-and-pl_sql-compatibility-comparison-for-malaysian-enterprises","status":"publish","type":"post","link":"https:\/\/47.250.123.25\/blog\/tech-blog\/oracle-database-migration-alternatives_-a-tco-and-pl_sql-compatibility-comparison-for-malaysian-enterprises\/","title":{"rendered":"Oracle Database Migration Alternatives_ A TCO and PL_SQL Compatibility Comparison for Malaysian Enterprises"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/kingbase-bbs.oss-cn-beijing.aliyuncs.com\/qywx\/blogImage\/2d079f2e-471a-4ba5-980a-b3336942c73b.png\" alt=\"A minimalist dark blue and cyan illustration of a glowing enterprise server rack representing database infrastructure.\" \/><\/p>\n<h2>The PL\/SQL Compatibility Matrix: What Migrates and What Requires Refactoring<\/h2>\n<p>For enterprise architects evaluating an <strong>oracle database migration<\/strong>, the primary friction point is rarely the data itself, but the logic embedded within stored procedures. The prevailing myth of a &quot;drop-in replacement&quot; often leads to underestimated migration costs when semantic differences in PL\/SQL are discovered post-deployment.<\/p>\n<p>KingbaseES, as a commercial database alternative, demonstrates significant compatibility with Oracle&#8217;s procedural language, yet it is not a byte-for-byte clone. The migration strategy must distinguish between features that map automatically and those requiring manual refactoring due to semantic divergence.<\/p>\n<h3>Supported Complex Types<\/h3>\n<p>KingbaseES supports the complex data structures most commonly used in Oracle PL\/SQL. This includes:<\/p>\n<ul>\n<li><strong>Record Types:<\/strong> <code>RECORD<\/code><\/li>\n<li><strong>Attributes:<\/strong> <code>%TYPE<\/code> and <code>%ROWTYPE<\/code><\/li>\n<li><strong>Collections:<\/strong> Associative arrays, variable arrays (VARRAYs), and nested tables.<\/li>\n<\/ul>\n<p>For developers, this means that a significant portion of existing application logic involving data structures can be migrated with minimal syntactic changes. The database engine is designed to interpret these constructs in a manner consistent with Oracle&#8217;s expectations for data typing and scope.<\/p>\n<h3>Semantic Gaps and Refactoring Needs<\/h3>\n<p>Despite high-level compatibility, specific semantic differences require manual intervention. These are not syntax errors but logic divergences that can alter query results if unaddressed:<\/p>\n<ol>\n<li><strong>Regularization Logic (<code>match_param<\/code>):<\/strong> Differences in how regular expressions handle the <code>match_param<\/code> argument can lead to different string matching results between Oracle and KingbaseES. Code relying on specific regex behaviors must be validated against KingbaseES test cases.<\/li>\n<li><strong>Time Type Handling:<\/strong> While both systems support <code>DATE<\/code> and <code>INTERVAL<\/code>, the internal representation and behavior of time types can differ. Migration projects must audit any logic dependent on specific time arithmetic or timezone conversions.<\/li>\n<li><strong>Proprietary Packages:<\/strong> While standard PL\/SQL is well-supported, specific Oracle proprietary packages (e.g., certain <code>DBMS_<\/code> packages) may not have direct equivalents in KingbaseES. These require either functional replacement using KingbaseES APIs or refactoring of the business logic.<\/li>\n<\/ol>\n<p><strong>Architectural Takeaway:<\/strong> Do not assume 100% compatibility. A &quot;lift-and-shift&quot; approach for PL\/SQL is viable only after a targeted audit of regularization logic and time-dependent procedures.<\/p>\n<h2>Data Type Mapping: Navigating Oracle Number and Time Type Divergences<\/h2>\n<p>Successful <strong>oracle database migration<\/strong> hinges on the integrity of the underlying data schema. KingbaseES is engineered to support the core data types found in Oracle, minimizing the need for schema restructuring. However, the mapping is not always one-to-one in terms of behavior, requiring careful validation during the schema conversion phase.<\/p>\n<h3>Supported Data Types<\/h3>\n<p>KingbaseES supports almost all Oracle-specific data types, ensuring that the physical structure of the database remains largely intact. The supported types include:<\/p>\n<ul>\n<li><strong>Numeric:<\/strong> <code>NUMBER<\/code><\/li>\n<li><strong>Character:<\/strong> <code>VARCHAR2<\/code>, <code>CHAR(n)<\/code><\/li>\n<li><strong>Temporal:<\/strong> <code>DATE<\/code>, <code>INTERVAL<\/code><\/li>\n<li><strong>Row Identifiers:<\/strong> <code>ROWID<\/code><\/li>\n<\/ul>\n<p>This broad support allows for a direct mapping of most tables without extensive data type redefinition.<\/p>\n<h3>Critical Divergences<\/h3>\n<p>The following table highlights specific areas where data behavior may diverge, necessitating pre-migration validation scripts:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Feature<\/th>\n<th style=\"text-align:left\">Oracle Behavior<\/th>\n<th style=\"text-align:left\">KingbaseES Behavior<\/th>\n<th style=\"text-align:left\">Migration Action Required<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Time Types<\/strong><\/td>\n<td style=\"text-align:left\">Specific handling of date arithmetic and precision.<\/td>\n<td style=\"text-align:left\">Similar support but potential differences in internal storage or precision limits.<\/td>\n<td style=\"text-align:left\">Validate time arithmetic logic in application code.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Regularization<\/strong><\/td>\n<td style=\"text-align:left\"><code>match_param<\/code> handling in regex functions.<\/td>\n<td style=\"text-align:left\">Semantic differences in <code>match_param<\/code> interpretation.<\/td>\n<td style=\"text-align:left\">Review and adjust regex logic in stored procedures.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>ROWID<\/strong><\/td>\n<td style=\"text-align:left\">Physical address of a row.<\/td>\n<td style=\"text-align:left\">Supported, but physical address semantics may differ.<\/td>\n<td style=\"text-align:left\">Audit queries relying on <code>ROWID<\/code> for performance optimization.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Interval<\/strong><\/td>\n<td style=\"text-align:left\">Interval arithmetic.<\/td>\n<td style=\"text-align:left\">Supported, but edge cases in arithmetic may vary.<\/td>\n<td style=\"text-align:left\">Test interval calculations in reporting and ETL jobs.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Recommendation:<\/strong> Before executing a full data migration, run a schema compatibility check using KingbaseES&#8217;s <strong>Oracle Data Type Compatibility Description<\/strong>. This document serves as the definitive guide for identifying any non-standard data type usage that may require conversion.<\/p>\n<h2>High Availability Architecture: Oracle RAC vs. KingbaseES HA\/DR Models<\/h2>\n<p>When moving from Oracle, the architectural shift in High Availability (HA) and Disaster Recovery (DR) is a critical consideration. Oracle Real Application Clusters (RAC) offers a shared-disk architecture that provides active-active capabilities, but it often requires significant infrastructure complexity and licensing overhead.<\/p>\n<h3>KingbaseES HA\/DR Capabilities<\/h3>\n<p>KingbaseES provides robust High Availability and Disaster Recovery capabilities designed for enterprise resilience. While the specific architectural implementation (e.g., shared-disk vs. shared-nothing) is not explicitly detailed in all public documentation, the system supports:<\/p>\n<ul>\n<li><strong>Real-time local disaster recovery:<\/strong> Ensuring data consistency across nodes.<\/li>\n<li><strong>HA Clustering:<\/strong> Redundant nodes to prevent single points of failure.<\/li>\n<\/ul>\n<h3>Comparative Context<\/h3>\n<p>To understand the operational implications, it is useful to compare KingbaseES&#8217;s approach to other enterprise standards, such as SQL Server&#8217;s Always On Availability Groups.<\/p>\n<ul>\n<li><strong>SQL Server Always On:<\/strong> Requires a specific cluster manager (Failover Clustering on Windows or Pacemaker on Linux) to coordinate availability groups.<\/li>\n<li><strong>KingbaseES:<\/strong> Offers HA\/DR support that integrates with the database&#8217;s native architecture. The documentation indicates a focus on system-level support for high availability, though the specific clustering mechanism (e.g., whether it relies on external cluster managers like Pacemaker or internal mechanisms) should be verified against the <strong>Overview of KingbaseES High Availability<\/strong> for the specific version in use.<\/li>\n<\/ul>\n<p><strong>Architectural Implication:<\/strong> While KingbaseES can meet the availability requirements of Oracle workloads, the operational model may differ. Enterprises must assess whether their existing DR runbooks need adjustment to align with KingbaseES&#8217;s failover and recovery procedures. The goal is to achieve similar RPO\/RTO targets without the overhead of Oracle RAC&#8217;s shared-disk infrastructure.<\/p>\n<h2>The TCO Equation: Licensing, Storage Efficiency, and Migration Labor<\/h2>\n<p>Total Cost of Ownership (TCO) for an <strong>oracle database migration<\/strong> extends beyond simple license substitution. It encompasses migration labor, long-term maintenance, and infrastructure efficiency. The financial case often relies on reducing the &quot;lock-in&quot; costs of Oracle while managing the transition effort.<\/p>\n<h3>Licensing and Cost Structure<\/h3>\n<p>KingbaseES is a commercial software product. Unlike open-source alternatives, it operates under a specific commercial licensing model. While the exact terms (e.g., per-core, subscription) are subject to vendor negotiation and specific contract terms, the commercial nature of the product ensures dedicated support and feature roadmaps.<\/p>\n<ul>\n<li><strong>Oracle:<\/strong> Typically involves complex, per-core licensing with high renewal costs.<\/li>\n<li><strong>KingbaseES:<\/strong> Offers a commercial alternative that can reduce licensing overhead, though specific savings must be calculated based on the enterprise&#8217;s current Oracle footprint and the target KingbaseES pricing structure.<\/li>\n<\/ul>\n<h3>Efficiency Claims and Conditions<\/h3>\n<p>Solution details indicate that KingbaseES deployments can achieve significant operational efficiencies under specific conditions:<\/p>\n<ul>\n<li><strong>Storage Cost Reduction:<\/strong> Claims of up to <strong>75% storage cost reduction<\/strong> are possible, likely driven by efficient compression algorithms or data structures. <em>Condition:<\/em> This applies to specific workload types and dataset sizes; it is not a universal guarantee for all data.<\/li>\n<li><strong>Cutover Speed:<\/strong> Complex cutovers can be completed in <strong>&lt;2 hours<\/strong>. <em>Condition:<\/em> This depends on network bandwidth, data volume, and the complexity of the schema.<\/li>\n<li><strong>Concurrency:<\/strong> The system supports <strong>1000+ concurrent connections<\/strong>, suitable for medium-to-large enterprise workloads.<\/li>\n<\/ul>\n<h3>TCO Calculation Model<\/h3>\n<p>To accurately assess the TCO, enterprises should model the following:<\/p>\n<ol>\n<li><strong>Migration Labor:<\/strong> Hours required for PL\/SQL refactoring (due to semantic gaps) and schema conversion.<\/li>\n<li><strong>Licensing Delta:<\/strong> The difference between Oracle license costs and KingbaseES commercial licensing.<\/li>\n<li><strong>Infrastructure Savings:<\/strong> Potential reductions in storage and compute due to the efficiency claims mentioned above.<\/li>\n<li><strong>Operational Overhead:<\/strong> Training costs for DBAs and developers transitioning from Oracle to KingbaseES.<\/li>\n<\/ol>\n<h2>Migration Strategy: Rehost, Replatform, or Refactor for Oracle Workloads<\/h2>\n<p>Selecting the right migration path is critical to managing risk. The choice depends heavily on the complexity of the PL\/SQL logic and the tolerance for downtime.<\/p>\n<h3>Decision Framework<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Strategy<\/th>\n<th style=\"text-align:left\">Description<\/th>\n<th style=\"text-align:left\">Suitability for KingbaseES<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Rehost (Lift-and-Shift)<\/strong><\/td>\n<td style=\"text-align:left\">Moving the database to KingbaseES with minimal code changes.<\/td>\n<td style=\"text-align:left\"><strong>Viable<\/strong> for applications using standard SQL and supported PL\/SQL types (RECORD, %ROWTYPE). Requires validation of regex and time logic.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Replatform<\/strong><\/td>\n<td style=\"text-align:left\">Moving to KingbaseES and optimizing for its specific features (e.g., indexing, partitioning).<\/td>\n<td style=\"text-align:left\"><strong>Recommended<\/strong> for workloads where storage efficiency and concurrency benefits can be leveraged.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Refactor (Re-architect)<\/strong><\/td>\n<td style=\"text-align:left\">Rewriting application logic to align with KingbaseES capabilities.<\/td>\n<td style=\"text-align:left\"><strong>Necessary<\/strong> if the application relies heavily on unsupported Oracle proprietary packages or specific semantic behaviors that cannot be mapped.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Migration Friction Checklist<\/h3>\n<p>Before committing to a strategy, evaluate the following:<\/p>\n<ul>\n<li class=\"task-list-item\"><strong>PL\/SQL Audit:<\/strong> Have all stored procedures been scanned for unsupported <code>match_param<\/code> logic or proprietary packages?<\/li>\n<li class=\"task-list-item\"><strong>Data Type Validation:<\/strong> Have time type and interval calculations been tested in the target environment?<\/li>\n<li class=\"task-list-item\"><strong>API Compatibility:<\/strong> Are the application&#8217;s JDBC\/ODC\/DCI\/ESQL connections verified against KingbaseES drivers?<\/li>\n<li class=\"task-list-item\"><strong>HA\/DR Testing:<\/strong> Has the failover process been simulated to ensure RTO targets are met?<\/li>\n<\/ul>\n<p><strong>Recommendation:<\/strong> For enterprises with complex legacy systems, a <strong>Replatform<\/strong> approach is often the sweet spot. It allows for the retention of most PL\/SQL logic while enabling the adoption of KingbaseES&#8217;s efficiency features, provided the semantic gaps are addressed during the planning phase.<\/p>\n<h2>Operational Reality: API Support and Skilled Personnel Availability<\/h2>\n<p>Post-migration success relies on the availability of development tooling and the operational expertise of the team. KingbaseES provides a comprehensive set of APIs to ensure application compatibility.<\/p>\n<h3>Developer Tooling<\/h3>\n<p>KingbaseES supports standard industry APIs, ensuring that existing application code can connect with minimal modification:<\/p>\n<ul>\n<li><strong>JDBC:<\/strong> For Java-based applications.<\/li>\n<li><strong>ODBC:<\/strong> For general-purpose connectivity.<\/li>\n<li><strong>DCI:<\/strong> For C\/C++ applications.<\/li>\n<li><strong>ESQL:<\/strong> For embedded SQL usage.<\/li>\n<\/ul>\n<p>These APIs are documented in the <strong>KingbaseES Database Development Guide<\/strong>, providing the necessary instructions for integration.<\/p>\n<h3>Personnel and Support Landscape<\/h3>\n<p>A critical constraint for <strong>oracle database migration<\/strong> is the availability of skilled personnel.<\/p>\n<ul>\n<li><strong>Oracle:<\/strong> Widely supported with a large ecosystem of certified professionals in the region.<\/li>\n<li><strong>KingbaseES:<\/strong> As a commercial product, it requires specific training and certification. While the product is globally available, there is no verified evidence of a dedicated local Malaysian office or a pre-existing pool of local engineers.\n<ul>\n<li><strong>Implication:<\/strong> Enterprises must plan for training their existing staff or engage with KingbaseES&#8217;s global support channels. The operational model may involve a mix of remote support and on-site training rather than immediate local presence.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Action Item:<\/strong> Procurement teams should include a budget for specialized training and support contracts to bridge the skills gap, ensuring the transition from Oracle to KingbaseES does not result in operational stagnation.<\/p>\n<h2>Conclusion: A Conditional Recommendation<\/h2>\n<p>The decision to migrate from Oracle to KingbaseES is not a binary choice of &quot;better or worse,&quot; but a strategic alignment of workload requirements with compatibility matrices.<\/p>\n<p><strong>Choose KingbaseES if:<\/strong><\/p>\n<ul>\n<li>Your workload relies heavily on standard PL\/SQL constructs (RECORD, %ROWTYPE) and you are willing to perform targeted refactoring for semantic differences (regex, time types).<\/li>\n<li>You seek a commercial alternative to reduce Oracle licensing costs and vendor lock-in.<\/li>\n<li>Your infrastructure requirements align with KingbaseES&#8217;s HA\/DR capabilities and storage efficiency claims.<\/li>\n<\/ul>\n<p><strong>Retain Oracle if:<\/strong><\/p>\n<ul>\n<li>Your system relies on extreme customization or proprietary Oracle features that have no equivalent in KingbaseES.<\/li>\n<li>Your organization lacks the resources to manage the migration friction of PL\/SQL refactoring.<\/li>\n<\/ul>\n<p><strong>Consider Other Options if:<\/strong><\/p>\n<ul>\n<li>You are building a greenfield project where PL\/SQL compatibility is not a constraint and open-source models are preferred.<\/li>\n<\/ul>\n<p>For enterprises, the path forward involves a disciplined evaluation of PL\/SQL friction and a realistic assessment of the TCO, rather than relying on the promise of a &quot;drop-in&quot; replacement.<\/p>\n<h2>FAQ<\/h2>\n<h3>Does KingbaseES support Oracle PL\/SQL packages without any modification?<\/h3>\n<p>KingbaseES supports most standard PL\/SQL constructs and complex types (like RECORD and %ROWTYPE), but specific proprietary Oracle packages and semantic differences in logic (such as <code>match_param<\/code> in regular expressions) often require manual adjustment. It is not a 100% automatic replacement for all Oracle logic.<\/p>\n<h3>What are the specific data type differences between Oracle and KingbaseES that affect migration?<\/h3>\n<p>While KingbaseES supports core types like <code>NUMBER<\/code>, <code>VARCHAR2<\/code>, and <code>DATE<\/code>, differences exist in how time types are handled internally and how specific interval arithmetic behaves. Additionally, the <code>match_param<\/code> logic in regex functions may yield different results, requiring validation of time-dependent and string-matching logic.<\/p>\n<h3>How does KingbaseES High Availability compare to Oracle RAC or SQL Server Always On?<\/h3>\n<p>KingbaseES supports High Availability and Disaster Recovery (HA\/DR) capabilities. While Oracle RAC uses a shared-disk architecture, KingbaseES offers HA\/DR solutions that may utilize different clustering mechanisms. Specific architectural details (e.g., cluster manager requirements) should be verified against the product documentation, as the operational model may differ from Oracle RAC.<\/p>\n<h3>Is KingbaseES a drop-in replacement for Oracle, or does it require application refactoring?<\/h3>\n<p>It is not a pure &quot;drop-in&quot; replacement. While data types and standard SQL are highly compatible, semantic differences in PL\/SQL logic (particularly regarding regularization and time types) necessitate a refactoring phase for stored procedures to ensure functional parity.<\/p>\n<h3>Does KingbaseES support vector search or AI workloads natively?<\/h3>\n<p>There is no verified evidence in the current documentation that KingbaseES includes a native vector engine, embedding capabilities, or hybrid search features. For AI\/RAG workloads, a separate vector store or external service is typically required, and KingbaseES should be treated as a transactional database rather than an AI-native vector store.<\/p>\n<hr \/>\n<p><strong>\ud83d\udca1 More Resources<\/strong><\/p>\n<p>If you would like to dive deeper into KingbaseES and its application practices across various industries, we have compiled the following official resources to help you get started quickly and develop and operate with efficiency:<\/p>\n<ul>\n<li><a href=\"https:\/\/bbs.kingbase.com.cn\/\">Kingbase Community<\/a>: A one-stop interactive platform for technical exchanges, Q&amp;A, and experience sharing\u2014join forces with fellow DBAs and developers.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Solution-Oracle.html\">Kingbase Solutions<\/a>: One-stop full-stack database migration and cloud-native solutions, supporting smooth migration of multi-source heterogeneous data, ensuring high availability, real-time integration, and sustained high performance.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Customers.html\">Kingbase Case Studies<\/a>: Real-world user scenarios and implementation outcomes, showcasing KingbaseES&#8217;s outstanding capabilities in high availability, high performance, and IT adaptation.<\/li>\n<li><a href=\"https:\/\/docs.kingbase.com.cn\/en\">Kingbase Documentation<\/a>: Authoritative and comprehensive product manuals and technical guides, covering the entire lifecycle from installation and deployment to development, programming, and operations management.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Download.html\">Free Download<\/a>: Get the latest installation packages, drivers, tools, and patches, supporting multiple platforms and domestic chip architectures.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/blog\/\">Digital Construction Encyclopedia<\/a>: Covers digital strategy planning, data integration, metrics management, database visualization applications, and more to empower enterprise digital transformation.<\/li>\n<\/ul>\n<p><strong>Open Source Resources:<\/strong><\/p>\n<ul>\n<li><a href=\"https:\/\/github.com\/hgsandy\/Kingbase-docs\">GitHub &#8211; Kingbase-docs<\/a>: Kingbase documentation open-source repository\u2014Stars and contributions are welcome.<\/li>\n<li><a href=\"https:\/\/gitee.com\/hgsandy\/kingbase-docs\">Gitee &#8211; Kingbase-docs<\/a>: Domestic mirror repository for Kingbase documentation for faster access.<\/li>\n<\/ul>\n<p>Welcome to explore the resources above and begin your Kingbase journey!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The PL\/SQL Compatibility Matrix: What Migrates and What Requires Refactoring For enterprise architects evaluating an oracle database migration, the primary friction point is rarely the data itself, but the logic&#8230;<\/p>\n","protected":false},"author":934,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-328","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/posts\/328","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/users\/934"}],"replies":[{"embeddable":true,"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/comments?post=328"}],"version-history":[{"count":0,"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/posts\/328\/revisions"}],"wp:attachment":[{"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/media?parent=328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/categories?post=328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/47.250.123.25\/blog\/wp-json\/wp\/v2\/tags?post=328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}