Databases 15 min read

Cloud-Native Database: Market Trends, Technical Evolution and Accessibility

Cloud-native databases, now backed by major providers and projected to power 95 % of digital business by 2025, are rapidly evolving from traditional systems to flexible, Kubernetes-compatible, MySQL/PostgreSQL-compatible, HTAP-enabled, serverless platforms—exemplified by Baidu’s GaiaDB with advanced consensus, low-latency networking, columnar storage, AI-driven operations—while enterprises balance adoption benefits against deployment, maturity, and sustainability concerns.

Baidu Geek Talk
Baidu Geek Talk
Baidu Geek Talk
Cloud-Native Database: Market Trends, Technical Evolution and Accessibility

Over the past half-century, database products have undergone significant evolution: from integrated mainframe databases to IOE architectures, then to open-source databases like MySQL, and finally to cloud databases. Currently, cloud-native databases have emerged as the future direction, gaining strong support from cloud providers like AWS, Alibaba Cloud, and Baidu Intelligent Cloud.

According to Gartner predictions, by 2025, 95% of digital business will be based on cloud-native platforms, driving rapid growth in the cloud-native database market. However, 42% of enterprises still have concerns about adopting cloud-native databases. Survey data shows 57.9% of enterprises consider using cloud-native databases for their primary business systems, while 42% remain观望. Internet行业 accounts for 55.4% of adoption, with finance, manufacturing, and consumer industries each below 10%.

The main concerns include: flexible deployment requirements (especially for government and financial sectors requiring 90% private deployment), technology maturity, and service sustainability. To achieve broader accessibility, cloud-native databases must improve across deployment, usage, and operations:

Deployment : Support cross-platform deployment on generic hardware, containerization via Kubernetes, and flexible single-node to distributed architectures

Usage : Maintain compatibility with MySQL/PostgreSQL, enable HTAP capabilities for hybrid transactional/analytical processing, and provide smooth migration paths

Operations : Implement automated backup, recovery, monitoring, fault detection, and leverage AI/ML for intelligent operations (AI4DB). Serverless capabilities enable automatic scaling of compute and storage resources

Baidu's GaiaDB exemplifies this evolution from 1.0 to 4.0. Key technical innovations include: Quorum consensus protocol replacing Raft to reduce network latency (single network request vs. two), intelligent network framework supporting kernel/user-space TCP with automatic protocol selection (reducing E2E latency by 60% to hundred-microsecond range), parallel computing technology for multi-core CPU utilization, and columnar storage indexes for efficient analytical queries.

GaiaDB 4.0 supports 1GB to 500TB storage scaling, 100% MySQL syntax and protocol compatibility, and HTAP capabilities for mixed workloads. The platform combines storage-compute separation with Serverless capabilities for automatic scaling and integrates large language models for intelligent operational assistance, helping database engineers efficiently retrieve knowledge and make rapid operational decisions.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

HTAPdatabase evolutionStorage Compute SeparationGaiaDBAI4DBdatabase accessibilityQuorum protocol
Baidu Geek Talk
Written by

Baidu Geek Talk

Follow us to discover more Baidu tech insights.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.