{"id":1190,"date":"2026-09-04T04:17:53","date_gmt":"2026-09-04T04:17:53","guid":{"rendered":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/enterprise-pl-sql-compatible-database-evaluation-criteria\/"},"modified":"2026-09-04T04:17:53","modified_gmt":"2026-09-04T04:17:53","slug":"enterprise-pl-sql-compatible-database-evaluation-criteria","status":"publish","type":"post","link":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/enterprise-pl-sql-compatible-database-evaluation-criteria\/","title":{"rendered":"Enterprise PL_SQL Compatible Database_ Evaluation Criteria"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/kingbase-bbs.oss-cn-beijing.aliyuncs.com\/qywx\/blogImage\/ae7912f9-d259-41ae-b4ac-592a52ecc385.webp\" alt=\"A precision calibration gauge resting on leather-bound engineering ledgers, symbolizing the technical validation of semantic equivalence in database migration.\" \/><\/p>\n<h2>Decision Framework: Workload, Stakeholders, and Evaluation Criteria<\/h2>\n<p>Before evaluating specific vendors like KingbaseES, organizations must define their workload requirements and stakeholder needs to establish a fair selection framework. This section outlines the weighted criteria, disqualifiers, and decision conditions necessary to select an <strong>enterprise pl\/sql compatible database<\/strong>.<\/p>\n<h3>1. Workload and Stakeholder Requirements<\/h3>\n<ul>\n<li><strong>Workload Profile<\/strong>: Define the complexity of PL\/SQL objects (stored procedures, functions, triggers, packages). Identify the volume of transactions and the criticality of ACID compliance.<\/li>\n<li><strong>Stakeholder Matrix<\/strong>:\n<ul>\n<li><strong>IT Operations<\/strong>: Requires validation of transaction consistency and system stability.<\/li>\n<li><strong>Business Units<\/strong>: Require 100% accuracy in business logic calculations (e.g., tax, interest) to prevent financial discrepancies.<\/li>\n<li><strong>Security\/Compliance<\/strong>: Require verified access controls and audit trail integrity.<\/li>\n<li><strong>Legal\/Regulatory<\/strong>: Require confirmation of data residency and regulatory compliance status.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>2. Weighted Evaluation Criteria<\/h3>\n<p>The following criteria should be weighted based on organizational priorities. Scores must be derived from verified evidence, not vendor marketing.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Criteria<\/th>\n<th style=\"text-align:left\">Weight<\/th>\n<th style=\"text-align:left\">Evidence Required<\/th>\n<th style=\"text-align:left\">Disqualifier Condition<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Semantic Equivalence<\/strong><\/td>\n<td style=\"text-align:left\">40%<\/td>\n<td style=\"text-align:left\">PoC results comparing Oracle baseline vs. target output for complex logic.<\/td>\n<td style=\"text-align:left\">Inability to demonstrate identical business logic results for critical paths.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Feature Coverage<\/strong><\/td>\n<td style=\"text-align:left\">25%<\/td>\n<td style=\"text-align:left\">Version mapping table showing support status for specific Oracle packages (e.g., <code>DBMS_AQ<\/code>, <code>DBMS_SCHEDULER<\/code>).<\/td>\n<td style=\"text-align:left\">Lack of support for mandatory proprietary features without a documented migration path.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Migration Tooling<\/strong><\/td>\n<td style=\"text-align:left\">15%<\/td>\n<td style=\"text-align:left\">Conversion success rates, error reporting mechanisms, and manual intervention estimates.<\/td>\n<td style=\"text-align:left\">Automated tools that fail to flag complex logic errors or require &gt;50% manual rewrite.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>TCO &amp; Licensing<\/strong><\/td>\n<td style=\"text-align:left\">10%<\/td>\n<td style=\"text-align:left\">Transparent breakdown of license costs (per core\/node) vs. estimated engineering hours.<\/td>\n<td style=\"text-align:left\">Assumption of cost savings without a defined workload comparison methodology.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Vendor Support<\/strong><\/td>\n<td style=\"text-align:left\">10%<\/td>\n<td style=\"text-align:left\">SLA terms for PL\/SQL debugging and migration assistance.<\/td>\n<td style=\"text-align:left\">Absence of specific support for PL\/SQL semantic issues.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>3. The Semantic Gap as a Disqualifier<\/h3>\n<p>The &quot;Semantic Gap&quot; refers to the difference between code that compiles successfully and code that executes with identical business logic results. Any vendor that cannot provide evidence of semantic equivalence testing for complex PL\/SQL logic should be considered a high-risk candidate. A &quot;drop-in&quot; migration promise is a false assumption if the vendor cannot prove that edge cases (e.g., package state persistence, specific exception handling) behave identically to the incumbent Oracle system.<\/p>\n<h2>Version Mapping: Oracle PL\/SQL Features vs. KingbaseES V8<\/h2>\n<p>To evaluate compatibility, organizations must verify specific feature support. The following table outlines the support status of key Oracle PL\/SQL features in KingbaseES V8 based on available documentation. Note that &quot;Partial&quot; support often requires manual refactoring.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Oracle Feature<\/th>\n<th style=\"text-align:left\">Support Status in KingbaseES V8<\/th>\n<th style=\"text-align:left\">Notes \/ Migration Implications<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Standard Stored Procedures &amp; Functions<\/strong><\/td>\n<td style=\"text-align:left\">Supported<\/td>\n<td style=\"text-align:left\">High syntax compatibility; semantic equivalence must be validated via PoC.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Triggers (Basic)<\/strong><\/td>\n<td style=\"text-align:left\">Supported<\/td>\n<td style=\"text-align:left\">Basic <code>BEFORE\/AFTER<\/code> triggers generally supported; complex logic requires review.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Package State (Session Variables)<\/strong><\/td>\n<td style=\"text-align:left\">Partial<\/td>\n<td style=\"text-align:left\">State persistence across calls may differ; requires verification of session behavior.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>DBMS_AQ (Advanced Queuing)<\/strong><\/td>\n<td style=\"text-align:left\">Partial\/Unsupported<\/td>\n<td style=\"text-align:left\">Often requires alternative messaging solutions or significant refactoring.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>DBMS_SCHEDULER (Complex Jobs)<\/strong><\/td>\n<td style=\"text-align:left\">Partial<\/td>\n<td style=\"text-align:left\">Complex job dependencies and specific scheduling features may need manual adjustment.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>DBMS_LOB (Blob Handling)<\/strong><\/td>\n<td style=\"text-align:left\">Partial<\/td>\n<td style=\"text-align:left\">Specific blob handling behaviors may differ; test required for large object operations.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Oracle-Specific Built-ins (e.g., NVL2, DECODE)<\/strong><\/td>\n<td style=\"text-align:left\">Supported<\/td>\n<td style=\"text-align:left\">Syntax supported; edge cases in null handling or rounding must be validated.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>REF CURSORs<\/strong><\/td>\n<td style=\"text-align:left\">Supported<\/td>\n<td style=\"text-align:left\">Behavior when passed between procedures or across schemas requires testing.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><em>Evidence Note: Specific version mapping data showing full feature parity is not fully documented in public sources. Buyers must request a detailed feature matrix from the vendor and validate via PoC.<\/em><\/p>\n<h2>The TCO Reality: License Costs vs. Engineering Debt<\/h2>\n<p>Total Cost of Ownership (TCO) for an <strong>enterprise pl\/sql compatible database<\/strong> migration must separate license savings from engineering debt. While KingbaseES is a commercial database product with licensing based on core or node metrics, assuming automatic cost savings is a risk.<\/p>\n<h3>Cost Components<\/h3>\n<ol>\n<li><strong>License and Infrastructure<\/strong>: KingbaseES is a commercial product, not open-source. Licensing costs are typically per core or per node.<\/li>\n<li><strong>Migration Engineering<\/strong>: Costs include automated conversion tool usage, manual code review, and refactoring of logic that the tool cannot handle.<\/li>\n<li><strong>Testing and Validation<\/strong>: The effort to build test suites that verify semantic equivalence is often the most underestimated cost.<\/li>\n<\/ol>\n<h3>TCO Comparison Methodology<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Cost Category<\/th>\n<th style=\"text-align:left\">Oracle Incumbent<\/th>\n<th style=\"text-align:left\">Alternative Candidate (e.g., KingbaseES)<\/th>\n<th style=\"text-align:left\">Verification Requirement<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Licensing<\/strong><\/td>\n<td style=\"text-align:left\">High (Per Core)<\/td>\n<td style=\"text-align:left\">Commercial (Per Core\/Node)<\/td>\n<td style=\"text-align:left\">Compare specific workload metrics; savings are not guaranteed.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Automated Conversion<\/strong><\/td>\n<td style=\"text-align:left\">N\/A<\/td>\n<td style=\"text-align:left\">Medium (Requires Review)<\/td>\n<td style=\"text-align:left\">Verify coverage rates and error reporting mechanisms.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Manual Refactoring<\/strong><\/td>\n<td style=\"text-align:left\">N\/A<\/td>\n<td style=\"text-align:left\">High (Complex Logic)<\/td>\n<td style=\"text-align:left\">Estimate hours based on complexity of existing packages.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Validation Testing<\/strong><\/td>\n<td style=\"text-align:left\">N\/A<\/td>\n<td style=\"text-align:left\">Very High (Semantic Gap)<\/td>\n<td style=\"text-align:left\">Requires rigorous PoC to measure semantic drift.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Support &amp; Maintenance<\/strong><\/td>\n<td style=\"text-align:left\">High (Enterprise)<\/td>\n<td style=\"text-align:left\">Variable (SLA dependent)<\/td>\n<td style=\"text-align:left\">Verify SLA terms for PL\/SQL debugging specifically.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Key Insight<\/strong>: License savings are not guaranteed. A lower per-core cost may be offset by higher engineering costs if the &quot;Semantic Gap&quot; requires extensive manual refactoring. Buyers must request a transparent breakdown of the commercial licensing model and a realistic estimate of refactoring hours based on their specific workload.<\/p>\n<h2>Stakeholder Alignment: Mapping PL\/SQL Risk to Business Impact<\/h2>\n<p>Migration is not solely an IT project. It requires alignment between IT, business units, and security teams to manage the risks of PL\/SQL migration.<\/p>\n<ul>\n<li><strong>IT Operations<\/strong>: Focus on transaction consistency (ACID) and system stability. The risk is data corruption or instability during cutover.<\/li>\n<li><strong>Business Units<\/strong>: Focus on calculation accuracy. The risk is &quot;semantic drift,&quot; where a stored procedure calculates values differently than before, leading to financial reporting errors.<\/li>\n<li><strong>Security &amp; Compliance<\/strong>: Focus on access control and audit trails. The risk is that the new database handles privileges differently, potentially leading to compliance failures.<\/li>\n<\/ul>\n<p><strong>Action<\/strong>: Create a shared risk matrix where stakeholders sign off on the acceptable level of risk. For example, the business unit must agree on the threshold for semantic match (e.g., 99.5% match) and the process for addressing the remaining deviation.<\/p>\n<h2>PoC Test Plan: Validating Semantic Equivalence<\/h2>\n<p>A Proof of Concept (PoC) for an <strong>enterprise pl\/sql compatible database<\/strong> must validate the semantic gap, not just syntax compatibility. The following steps define a rigorous validation process.<\/p>\n<h3>Step 1: Select Representative Workload<\/h3>\n<p>Choose 50 to 100 stored procedures, functions, and triggers covering the full spectrum of complexity, including simple queries, complex joins, and heavy exception handling.<\/p>\n<h3>Step 2: Run Automated Conversion<\/h3>\n<p>Use the vendor&#8217;s migration tool (e.g., KMS) to convert the code. Record the conversion success rate and the number of errors flagged.<\/p>\n<h3>Step 3: Manual Review and Refactoring<\/h3>\n<p>Have developers review the converted code. Identify packages requiring manual intervention and estimate the hours spent. <em>Note: Refactoring hours depend on workload complexity and require PoC validation.<\/em><\/p>\n<h3>Step 4: Execute Functional Tests<\/h3>\n<p>Run the converted code against a test dataset mirroring production data. Compare output results (row counts, calculated values, error messages) against the Oracle baseline.<\/p>\n<h3>Step 5: Stress Test Transaction Consistency<\/h3>\n<p>Run the workload under heavy load to verify ACID properties. Check for deadlocks, rollback behaviors, and isolation level violations.<\/p>\n<h3>Step 6: Analyze Error Propagation<\/h3>\n<p>Intentionally trigger errors in stored procedures. Verify that error messages and stack traces match Oracle behavior or are clearly documented deviations.<\/p>\n<p><strong>Success Criteria<\/strong>: The candidate passes only if the output matches the Oracle baseline for all critical business logic paths. Any deviation indicates a semantic gap that must be addressed before production deployment.<\/p>\n<h2>Regulatory and Compliance: Data Residency and PDPA<\/h2>\n<p>Organizations in Malaysia must consider data residency and regulatory compliance.<\/p>\n<ul>\n<li><strong>PDPA and Data Residency<\/strong>: Malaysia&#8217;s Personal Data Protection Act (PDPA) does not create a blanket data-residency mandate requiring all data to reside within the country. However, specific industry regulations or internal policies may impose such requirements.<\/li>\n<li><strong>KingbaseES Compliance Status<\/strong>: There is no documented evidence of specific local regulatory approvals or certifications for KingbaseES in the Malaysian market.<\/li>\n<li><strong>Local Presence<\/strong>: Claims regarding local offices, data centers, or engineering teams in Malaysia must be verified directly with the vendor. Do not assume local presence based on marketing materials.<\/li>\n<\/ul>\n<h2>Vendor Reliability Scorecard: Support and Regional Verification<\/h2>\n<p>When evaluating a vendor like KingbaseES, verify the following capabilities. This scorecard emphasizes verification over assumption.<\/p>\n<ul>\n<li><strong>PL\/SQL Expertise<\/strong>: Does the support team have deep expertise in Oracle PL\/SQL semantics? Can they assist in debugging complex triggers?<\/li>\n<li><strong>Migration Assistance<\/strong>: Does the vendor provide dedicated engineers for migration, or is it purely self-service?<\/li>\n<li><strong>Regional Support<\/strong>: For organizations in Malaysia, verify support channels. Local or regional engineering presence can reduce response times, but this is a variable to be verified, not a standard feature.<\/li>\n<li><strong>SLA Specificity<\/strong>: Review SLAs for critical severity issues. Ensure they cover PL\/SQL debugging and migration support, not just general database uptime.<\/li>\n<\/ul>\n<h2>Go\/No-Go Decision Matrix<\/h2>\n<p>Use this matrix to determine whether to proceed with KingbaseES or consider other options based on the Semantic Gap analysis.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Decision Factor<\/th>\n<th style=\"text-align:left\">Go (Proceed)<\/th>\n<th style=\"text-align:left\">No-Go (Re-evaluate)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Semantic Equivalence<\/strong><\/td>\n<td style=\"text-align:left\">PoC confirms identical business logic for 100% of critical paths.<\/td>\n<td style=\"text-align:left\">PoC reveals unresolvable semantic drift in critical logic.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Feature Coverage<\/strong><\/td>\n<td style=\"text-align:left\">All mandatory Oracle features are Supported or have a clear migration path.<\/td>\n<td style=\"text-align:left\">Mandatory features (e.g., <code>DBMS_AQ<\/code>) are Unsupported with no workaround.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Engineering Effort<\/strong><\/td>\n<td style=\"text-align:left\">Refactoring hours are within budget and timeline.<\/td>\n<td style=\"text-align:left\">Estimated refactoring hours exceed budget or timeline significantly.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Local Compliance<\/strong><\/td>\n<td style=\"text-align:left\">Vendor confirms data residency options and local support availability.<\/td>\n<td style=\"text-align:left\">Vendor cannot confirm data residency or local support capabilities.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>TCO<\/strong><\/td>\n<td style=\"text-align:left\">Total cost (License + Engineering) is favorable compared to Oracle.<\/td>\n<td style=\"text-align:left\">Engineering costs outweigh license savings.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>FAQ<\/h2>\n<h3>What specific PL\/SQL features are non-compatible and require manual rewriting?<\/h3>\n<p>Features such as complex package state management, proprietary <code>DBMS_*<\/code> packages (e.g., <code>DBMS_AQ<\/code>), and specific Oracle built-in functions often require manual rewriting. While syntax may be compatible, runtime behavior differences necessitate code changes to ensure semantic equivalence.<\/p>\n<h3>How does the vendor&#8217;s support model handle critical production incidents in Malaysia?<\/h3>\n<p>Support models vary by vendor. Some offer global support with regional escalation paths, while others may have local engineering teams. Organizations must verify specific SLA terms and response times for their region directly with the vendor. Do not assume local presence without direct confirmation.<\/p>\n<h3>What is the estimated effort and risk for migrating complex triggers and stored procedures?<\/h3>\n<p>The effort depends on the complexity of the existing codebase. Automated tools can handle simple syntax, but complex logic often requires significant manual refactoring. The risk lies in the &quot;semantic gap,&quot; where code compiles but behaves differently. A PoC is required to estimate the actual effort.<\/p>\n<h3>Which vendors provide transparent TCO models that include migration and licensing?<\/h3>\n<p>Commercial vendors typically provide licensing models based on cores or nodes. However, a transparent TCO model must explicitly separate license costs from engineering migration costs. Buyers should request a detailed breakdown of expected refactoring hours and testing effort.<\/p>\n<h3>How do we verify semantic equivalence after automated code conversion?<\/h3>\n<p>Verification requires a rigorous PoC. Run the converted code against a production-like dataset and compare the output results (calculations, row counts, error messages) against the Oracle baseline. Any deviation indicates a semantic gap that must be addressed before production deployment.<\/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>Decision Framework: Workload, Stakeholders, and Evaluation Criteria Before evaluating specific vendors like KingbaseES, organizations must define their workload requirements and stakeholder needs to establish a fair selection framework. This section&#8230;<\/p>\n","protected":false},"author":2072,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"meta_description":"","_kingbase_seo_description":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-1190","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/1190","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/users\/2072"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/comments?post=1190"}],"version-history":[{"count":0,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/1190\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/media?parent=1190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/categories?post=1190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/tags?post=1190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}