- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Release of New Upgrade Mechanism for Kernel Minor Version
- Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Sales Suspension of Some General Specifications
- Announcement on Some APIs Integrated with CAM Authentication
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Change of Part of Parameters
- Announcement on Update of Database Audit Feature
- Announcement on Authentication of a Newly Added API Interface of Database Audit
- Announcement on Change of Public Network Linkage
- TDSQL-C for MySQL Audit Service Update
- Announcement on Supplementary Charge for Clusters with Pay-as-You-Go Storage Billing Mode
- Announcement on New APIs Integrated with CAM Permissions
- Announcement on the Release of New Version of Database Proxy
- Emergency Fix for Certain Monitoring Metrics
- Monitoring Metric Optimization
- Change to Database Audit Resource ID
- Ops Change
- Storage Price Adjustment Notification
- Beginner's Guide
- Product Introduction
- Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Columns Syntax
- Correlated Subquery Result Cache
- Global Index
- Binlog Write Optimization
- Large Transaction Binlog Optimization
- Binlog Purging Performance Optimization
- Optimization of Plan Caching Point Query
- Auto-Increment Column Persistence
- Invisible Index
- Computation Pushdown
- Parallel Initialization of InnoDB Buffer Pool
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Getting Started
- Database Audit
- Serverless Service
- Operation Guide
- Switching Cluster Page View in Console
- Database Connection
- Instance Management
- Configuration Adjustment
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Overview
- Use Limits
- Database Proxy Kernel Features
- Managing Database Proxy
- Enabling Database Proxy
- Setting Database Proxy Address
- Modifying or Deleting Connection Addresses
- Viewing and Changing the Access Policy
- Rebalancing the Load
- Transaction Split Feature
- Access Mode
- Adjusting Database Proxy Configuration
- Switching Database Proxy Network
- Viewing Database Proxy Monitoring Data
- Disabling Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Read-Only Analysis Engine
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Operation Log
- Data Migration
- Parallel Query
- Database Security and Encryption
- Monitoring and Alarms
- Basic SQL Operations
- Connecting to TDSQL-C for MySQL Through SCF
- Tag
- Practical Tutorial
- Classified Protection Practice for Database Audit of TDSQL-C for MySQL
- Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
- Usage Instructions for TDSQL-C MySQL
- New Version of Console
- Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
- Strengths of Database Proxy
- Selecting Billing Mode for Storage Space
- Creating Remote Disaster Recovery by DTS
- Creating VPC for Cluster
- Data Rollback
- Solution to High CPU Utilization
- How to Authorize Sub-Users to View Monitoring Data
- White Paper
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Billing APIs
- Instance APIs
- CloseClusterPasswordComplexity
- CopyClusterPasswordComplexity
- DescribeClusterDetail
- DescribeClusterPasswordComplexity
- ModifyClusterPasswordComplexity
- OpenClusterPasswordComplexity
- UpgradeClusterVersion
- UpgradeInstance
- SetRenewFlag
- OfflineCluster
- ModifyMaintainPeriodConfig
- IsolateInstance
- IsolateCluster
- DescribeMaintainPeriod
- DescribeInstanceSpecs
- DescribeClusters
- CreateClusters
- AddInstances
- OfflineInstance
- DescribeInstanceDetail
- DescribeClusterInstanceGrps
- DescribeInstances
- ActivateInstance
- ModifyInstanceName
- ModifyClusterName
- SearchClusterTables
- SearchClusterDatabases
- RestartInstance
- Multi-AZ APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- CloseWan
- CreateClusterDatabase
- DeleteClusterDatabase
- DescribeClusterDetailDatabases
- ModifyClusterDatabase
- OpenWan
- SwitchClusterVpc
- OpenReadOnlyInstanceExclusiveAccess
- OpenClusterReadOnlyInstanceGroupAccess
- ModifyDBInstanceSecurityGroups
- DescribeProjectSecurityGroups
- DescribeDBSecurityGroups
- SwitchProxyVpc
- DescribeFlow
- DescribeZones
- ModifyVipVport
- Data Types
- Error Codes
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
- Glossary
- Contact Us
- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Release of New Upgrade Mechanism for Kernel Minor Version
- Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Sales Suspension of Some General Specifications
- Announcement on Some APIs Integrated with CAM Authentication
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Change of Part of Parameters
- Announcement on Update of Database Audit Feature
- Announcement on Authentication of a Newly Added API Interface of Database Audit
- Announcement on Change of Public Network Linkage
- TDSQL-C for MySQL Audit Service Update
- Announcement on Supplementary Charge for Clusters with Pay-as-You-Go Storage Billing Mode
- Announcement on New APIs Integrated with CAM Permissions
- Announcement on the Release of New Version of Database Proxy
- Emergency Fix for Certain Monitoring Metrics
- Monitoring Metric Optimization
- Change to Database Audit Resource ID
- Ops Change
- Storage Price Adjustment Notification
- Beginner's Guide
- Product Introduction
- Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Columns Syntax
- Correlated Subquery Result Cache
- Global Index
- Binlog Write Optimization
- Large Transaction Binlog Optimization
- Binlog Purging Performance Optimization
- Optimization of Plan Caching Point Query
- Auto-Increment Column Persistence
- Invisible Index
- Computation Pushdown
- Parallel Initialization of InnoDB Buffer Pool
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Getting Started
- Database Audit
- Serverless Service
- Operation Guide
- Switching Cluster Page View in Console
- Database Connection
- Instance Management
- Configuration Adjustment
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Overview
- Use Limits
- Database Proxy Kernel Features
- Managing Database Proxy
- Enabling Database Proxy
- Setting Database Proxy Address
- Modifying or Deleting Connection Addresses
- Viewing and Changing the Access Policy
- Rebalancing the Load
- Transaction Split Feature
- Access Mode
- Adjusting Database Proxy Configuration
- Switching Database Proxy Network
- Viewing Database Proxy Monitoring Data
- Disabling Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Read-Only Analysis Engine
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Operation Log
- Data Migration
- Parallel Query
- Database Security and Encryption
- Monitoring and Alarms
- Basic SQL Operations
- Connecting to TDSQL-C for MySQL Through SCF
- Tag
- Practical Tutorial
- Classified Protection Practice for Database Audit of TDSQL-C for MySQL
- Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
- Usage Instructions for TDSQL-C MySQL
- New Version of Console
- Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
- Strengths of Database Proxy
- Selecting Billing Mode for Storage Space
- Creating Remote Disaster Recovery by DTS
- Creating VPC for Cluster
- Data Rollback
- Solution to High CPU Utilization
- How to Authorize Sub-Users to View Monitoring Data
- White Paper
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Billing APIs
- Instance APIs
- CloseClusterPasswordComplexity
- CopyClusterPasswordComplexity
- DescribeClusterDetail
- DescribeClusterPasswordComplexity
- ModifyClusterPasswordComplexity
- OpenClusterPasswordComplexity
- UpgradeClusterVersion
- UpgradeInstance
- SetRenewFlag
- OfflineCluster
- ModifyMaintainPeriodConfig
- IsolateInstance
- IsolateCluster
- DescribeMaintainPeriod
- DescribeInstanceSpecs
- DescribeClusters
- CreateClusters
- AddInstances
- OfflineInstance
- DescribeInstanceDetail
- DescribeClusterInstanceGrps
- DescribeInstances
- ActivateInstance
- ModifyInstanceName
- ModifyClusterName
- SearchClusterTables
- SearchClusterDatabases
- RestartInstance
- Multi-AZ APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- CloseWan
- CreateClusterDatabase
- DeleteClusterDatabase
- DescribeClusterDetailDatabases
- ModifyClusterDatabase
- OpenWan
- SwitchClusterVpc
- OpenReadOnlyInstanceExclusiveAccess
- OpenClusterReadOnlyInstanceGroupAccess
- ModifyDBInstanceSecurityGroups
- DescribeProjectSecurityGroups
- DescribeDBSecurityGroups
- SwitchProxyVpc
- DescribeFlow
- DescribeZones
- ModifyVipVport
- Data Types
- Error Codes
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
- Glossary
- Contact Us
This document introduces the new read-only analysis engine feature of TDSQL-C for MySQL, which is implemented based on the LibraDB engine.
Note:
The read-only analysis engine is currently in free beta testing. To apply for trial, click Submit a Ticket for handling.
Background
As a cloud-native database product, TDSQL-C for MySQL has undergone extensive optimization to support high concurrency, strong consistency, and enterprise-level database characteristics. It supports high-performance online transaction processing capabilities based on the TXSQL engine. However, in addition to using databases for high QPS online transactions, many business systems also require mining data and utilizing databases for data analysis, to help enterprises better make business decisions and drive the iterative innovation of businesses for quickly adapting to the market environment changes.
To support the high-performance online transaction processing capabilities and ensure the stability of business queries, traditional databases typically select row-based storage and adopt the Volcano model for execution, so they cannot efficiently serve analytical queries. Certainly, in some businesses, the traditional database + data warehouse solution is selected to support hybrid transaction/analytical processing, but this solution requires high maintenance costs. Moreover, customers need to build the ETL tools from the database to the data warehouse by themselves, and the real-time performance and consistency requirements for the data cannot be well satisfied.
Therefore, Tencent Cloud Native Database TDSQL-C for MySQL newly supports this read-only analysis engine feature, providing you with efficient and real-time data analysis services.
What Is a Read-Only Analysis Engine
The read-only analysis engine is a new feature supported by TDSQL-C for MySQL. This feature is implemented based on the LibraDB engine and provides services based on read-only instances. Its pluggable engine design allows for flexible creation and termination, and meanwhile provides you with massive data processing and efficient real-time complex analysis capabilities.
Feature Strengths
High-Speed Analysis Engine LibraDB
The LibraDB engine supports complex query analysis on TB-level data with a very low execution latency, enabling your business analytics system to efficiently extract useful information from massive databases. The LibraDB engine supports vectorized engines, large-scale parallel execution, and other acceleration features for analytical queries. No matter in multi-table JOIN and data aggregation and sorting of super-large tables, or in complex nested SQL queries, the LibraDB engine can provide excellent performance experience.
Pluggable Analysis Engine
The LibraDB engine is compatible with MySQL protocols and syntax, allowing you to directly execute complex query statements in LibraDB without modifying the business logic. You can also determine whether to enable the read-only analysis engine based on actual business situations, and disable it at any time to control costs when analytics acceleration is not required.
Real-Time Columnar Data Loading Capability
Through the built-in data synchronization components of the LibraDB engine, the existing data in TDSQL-C for MySQL can be quickly loaded into the read-only analysis engine. After data loading is completed, any changes to the data in the read-write instance can also be synchronized in real time, achieving real-time consistency for row and column data. Additionally, for inefficient data changes in traditional columnar storage scenarios with high concurrency data updates and deletions, the LibraDB engine provides the columnar storage capability for high concurrency data updates, which can support real-time data synchronization to achieve zero latency.
Specified Data Loading Capability
For traditional read-only instances, all data of the primary database needs to be synchronized to the secondary database. However, for the read-only analysis engine, it supports loading specified objects into the analysis engine rather than loading all objects. You can specify the databases and tables that require acceleration through the read-only analysis engine or those with data analysis value, and load them into the read-only analysis engine for data analysis, so as to flexibly control the disk space used by the read-only analysis engine.
Ultra-High Data Compression Rate
Based on the columnar storage structure, it provides both the ultra-high data scanning performance and an average compression ratio of 4-5 times, significantly reducing the storage costs.
Perfect Cloud Hosting Capabilities
Through fully hosted product design, you can experience the out-of-the-box data analysis capabilities, with no need to consider the complex ETL logic or backend database operations. Additionally, the comprehensive monitoring feature achieves meticulous filtering of core metrics from TXSQL to the analysis engine, and from the link layer to the storage layer, to simplify your operations, help you quickly understand the instance health status through key metrics, and provide effective optimization guide for the use of business systems. Furthermore, you can set custom threshold alarms to prevent potential exceptions in advance.
Applicable Scenarios
The read-only analysis engine aims to provide real-time, high-performance data analysis, helping you solve the complex Ops difficulties of data synchronization with self-built ETL tools. The read-only analysis engine feature enables you to easily and quickly build data analysis instances as the basis for making business decisions, so as to fully leverage the value of data.
Report Analysis and Real-Time Dashboard
SQL queries are complex in unfixed query modes, with a high throughput and a large volume of online data in scenarios such as data analysis for business operation and reporting systems for internal enterprise analyzers and managers, which support timely viewing the online operation status of business systems in real time. Read-only analysis engines can be used to meet the real-time and high-performance requirements of these scenarios.
User Reputation and Behavior Analysis
In scenarios such as advertising business and game operations, deep analysis is often required on the user behavior and user reputation. The analysis results are used for real-time operational decision-making. These scenarios involve a large volume of data and high QPS, and require timely return of data analysis results. By using a read-only analysis engine, you can quickly obtain the necessary data for user behavior analysis, which serves as the decision basis for precise push of related businesses.
Real-Time Data Warehouse
Read-only analysis engines can also be used to achieve ultra-high complex query performance in scenarios such as data analysis of e-commerce promotional orders, waybill analysis of the logistics industry, performance analysis of the financial industry, metric calculation, live streaming quality analysis, advertisement push analysis, intelligent driving cabin analysis, and probe analysis.
Big Data Reconciliation and Batch Computing
In some online businesses, especially in business scenarios related to money, it is necessary to perform scheduled reconciliation calculations for data statistics and merging. Batch computing of traditional row-based data results in a low reconciliation efficiency, high resource consumption, and failure to quickly meet business expectations. Read-only analysis engines with the ultra-strong concurrent computing capability can be used to meet the business requirements at an extremely high efficiency.
Yes
No
Was this page helpful?