Halo Database pioneered a plugin-based kernel architecture that adapts to different application scenarios through configuration, providing full-scenario coverage capabilities.
Migration of existing system databases typically faces:
Very time-consuming and requires substantial resources
Need to modify large amounts of application code to adapt to the new database
Performance after migration is uncertain
Migration carries high risk, high cost, and takes long time
Migrate database objects and data from Oracle/MySQL to Halo quickly
Zero or minimal code changes to complete database switch
Complete database version upgrade without downtime
Significantly reduce database procurement and maintenance costs


New Generation General-Purpose Unified Database System
Native kernel-level compatibility with SQL syntax and communication protocols of multiple databases
New Generation General-Purpose Unified Database System

Theoretically can achieve compatibility with any database
Achieve master-slave, cluster, sharding architectures through configuration
Comprehensive performance more than 50% higher compared to similar products
"1+1" i.e., 1 platform + 1 core database product, creating a one-stop data processing platform
We understand not only products but also business, creating end-to-end one-stop professional services
Support more complex SQL syntax (complex association, complex aggregation, etc.), and optimize for the performance of SQL and procedural languages
Supports one-click deployment via command line


Rich performance views
Professional diagnostic tools (HWR)
Supports multi-dimensional observation


A proprietary technology developed by our company, achieving multi-platform compatibility through native kernel-level implementation. For systems built on databases such as Oracle, MySQL, PostgreSQL, it can significantly reduce application code modifications. Based on current migration practices, it can reduce code modifications by at least 98% or even achieve migration without code modification, thereby greatly reducing migration costs and time, while also significantly lowering migration risks and protecting existing investments.

Supports multiple database communication protocols
Responsible for syntax and semantic parsing of SQL statements
Responsible for generating execution plans
Responsible for executing execution plans
Each multi-mode engine provides complete implementation from compilation to optimization to execution. Therefore, the multi-mode engine is not just shallow compatibility at the syntax level, but deep, comprehensive compatibility across database protocol, syntax parsing, optimizer, and executor, enabling smooth migration for systems built on databases such as Oracle, MySQL, and PostgreSQL.
Simply configure to switch between different database modes
Native kernel implementation, no additional performance overhead
Supports all kernel functions
Taking Halo[MySQL] as an example, Halo implements support for the MySQL communication protocol and commonly used MySQL syntax, enabling applications developed based on MySQL to communicate with Halo with almost no code rewriting.

MySQL Native CLI communicates with Halo

MySQL GUI Tool (dbeaver) communicates with Halo
Driver Interface Compatibility Technology
Although multi-mode compatibility technology can achieve deep compatibility with SQL, PL/SQL syntax, and database objects of different databases, it still cannot avoid modifying application code during application migration. Therefore, we have innovatively developed compatibility technology for JDBC and .Net driver interfaces. For closed commercial database software like Oracle, we have achieved compatibility with its proprietary driver interface classes based on its public documentation, truly realizing application code 'zero' modification.
Oracle driver interface compatibility technology
Truly achieve 'zero' application code modification

Driver-Level Compatibility Technology
Supports Oracle, MySQL, and PostgreSQL, the three mainstream databases
Using Storage-Compute Separation Architecture
Work nodes and data nodes use private communication protocol to avoid multiple parsing
DLB itself can achieve load balancing and high availability through LVS, f5, etc.
Uses storage-compute separation architecture to avoid distributed lock issues
Transparent to applications, no code modification required


When a RO node detects a write operation, it redirects the operation to the RW node
① Application initiates an UPDATE operation
② RO node detects this as a write operation and redirects it to the RW node
③ RW node executes the write operation and returns the result to the RO node
④ RO node returns the result to the application
Uses storage-compute separation architecture
Flexible sharding strategies (hash/range/list)
Intelligent condition pushdown
Automatic shard pruning
Parallel data writing


Through soft parsing technology, reduce the number of hard parses, save CPU resources, and improve SQL execution performance
Reduces number of hard parses
Saves CPU resources
Improves SQL execution performance

Can divide slave databases into multiple groups, each group containing one or more slaves. Different groups can set different synchronization levels, improving overall cluster performance and ensuring RPO=0

Taking 1 master 2 slave synchronous replication (cache consistency) as an example
Ensure Zero Data Loss, Guarantee Business Continuity
Cross-region distribution, data consistency guarantee, automatic failover
GDD enables any node to read and write, allowing businesses to access the nearest node
Uses RAFT protocol to ensure strong data consistency
Node failure triggers automatic business and data failover without manual intervention

When any data center fails, business traffic is automatically and intelligently routed to surviving data centers, achieving minute-level recovery and ensuring uninterrupted business
Breaks the traditional master-standby model, all remote nodes can carry production read/write traffic, transforming disaster recovery resources from 'cost centers' to 'business capability centers'
DataOS - Kernel-level AI support, greatly shortening the distance between models and data

Greatly shortens the distance between models and data
Real-time vectorization integrated in database
Integrated recall and re-ranking, intelligent relation generation
Vector similarity search with multiple distance metrics
Model version management, one-click rollback

Over 50% higher comprehensive performance compared to international products
Fast migration, seamless compatibility, superior performance - start your database localization journey