Hologres:Hologres instance selection

Instance type

Resource type

Core requirement

Applicable scenario

Virtual warehouse instance (recommended)

Exclusive computing resources and storage resources

• Supports high-performance, high-concurrency, and large-scale data processing.

• Implements a read/write splitting architecture in a single instance.

• Large-scale data services with data volumes at the TB or PB level, and frequent complex queries.

• High-concurrency online services with millisecond-level response requirements (above 1000 QPS).

• Mixed workload isolation, such as OLAP queries and real-time writing, or resource isolation requirements for multiple lines-of-business.

• Elastic scaling requirements, such as significant traffic fluctuations (periodic peaks) that require rapid scaling.

Serverless instance

Shared computing resources, and exclusive storage resources

• Supports high-performance, large-scale, and low-frequency data processing and data queries.

• Development or testing environments.

• Low-frequency and high-performance query scenarios.

• Scenarios with significant business load fluctuations, unpredictable peaks, and difficulty in reserving exclusive computing resources in advance.

General-purpose instance

Exclusive computing resources and storage resources

• Supports cost control and lightweight analysis.

• Supports upgrades to virtual warehouse instances.

• Smaller data volume (below TB level).

• Lightweight analysis, such as low-frequency ad hoc queries, and small to medium-scale BI report generation.

• Cost-sensitive businesses, such as limited budget requiring high cost-effectiveness solutions. Non-core business trial stages.

• Low-concurrency services, such as internal data service platforms. Scheduled task processing.

Read-only secondary instance (to be deprecated)

Exclusive computing resources and storage resources

• Supports the multi-instance read/write splitting architecture.

• Associates read-only secondary instances with a general-purpose instance.

• To be deprecated. Virtual warehouse instances are recommended.

• General-purpose primary instances serve as data writing and data processing instances, while read-only secondary instances serve as data analysis instances, ensuring read/write splitting.

Shared Cluster (Lakehouse Acceleration Edition) (to be deprecated)

Shared computing resources, and no storage resources

• Supports low-cost acceleration for lakehouse data queries and BI integration.

• No need for read and write operations on Hologres internal tables.

• Scenarios where data is stored in OSS or MaxCompute and you want to use Hologres for accelerated queries.

• Scenarios with burst large queries where reserved exclusive instance resources are insufficient.

• Scenarios requiring BI tools to accelerate lakehouse data queries. Hologres Shared Cluster can be used to connect with Tableau, Quick BI, FineBI, and other BI tools.