baidu/BaikalDB

BaikalDB, A Distributed HTAP Database.

Owned by Baidu

View on GitHub ↗Jump to charts ↓

baidu/BaikalDB has 1k+ stars and 150+ forks on GitHub, is written in C++, and was last pushed on Jun 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 23 minutes ago
Added to GitGenius on October 12th, 2026
Created on August 3rd, 2018
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 174
Total Stargazers: 1,240 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 247.2 days
Mean response time: 185.0 days
90th percentile: 305.8 days
Tracked items: 3

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

BaikalDB is a distributed HTAP database that combines transactional and analytical workloads on petabyte-scale data.

The database addresses the need for systems that handle both real-time read/write operations and complex analytical queries without requiring separate infrastructure. It achieves this by implementing projections, filter operators, aggregation operators, and sort operators within a single SQL engine. The system is compatible with the MySQL protocol and supports MySQL-style SQL, allowing users to migrate existing MySQL deployments without rewriting applications. Full-text search capability is built in through inverted indices with word segmentation, and fuzzy search is available via FULLTEXT KEY indexes and LIKE clauses. The tool can scan and aggregate hundreds of millions of rows in seconds.

Organizations should consider BaikalDB if they need to consolidate transactional and analytical workloads on large datasets while maintaining MySQL compatibility. It suits projects that want to avoid maintaining separate OLTP and OLAP systems and can benefit from seamless migration paths from existing MySQL infrastructure. The project is particularly relevant for teams already invested in the MySQL ecosystem who need analytical capabilities without operational complexity.

The project shows sustained development activity with regular updates to core functionality. The codebase demonstrates integration with established systems like RocksDB, brpc, and braft, indicating a focus on leveraging proven infrastructure components. The team maintains active engagement with the community through documentation and support channels, including dedicated communication groups for users seeking assistance.