Differences between ApsaraDB for ClickHouse Enterprise Edition and ApsaraDB for ClickHouse Community-compatible Edition - ApsaraDB for ClickHouse

This topic describes the differences between ApsaraDB for ClickHouse Enterprise Edition and ApsaraDB for ClickHouse Community-compatible Edition in terms of architecture and engine versions.

Architectures

Architecture of Enterprise Edition

ApsaraDB for ClickHouse Enterprise Edition uses a cloud-native architecture in which computing and storage resources are separated. In addition, both computing and storage resources are managed in Serverless mode. This allows for on-demand usage of computing and storage resources. The following section describes the detailed characteristics:

Computing resources: Within a specified scaling range, the computing resources are automatically scaled based on loads to avoid resource waste and reduce database O&M costs.
Storage resources: Object Storage Service (OSS) is used. The data redundancy mechanism of OSS ensures high data availability. The unit price for storage of Enterprise Edition is significantly lower than that of Community-compatible Edition.

Enhanced features

Feature	Description
Compute-storage separation	Storage and computing resources are separately managed to implement flexible resource management.
Scalability	Both storage resources and computing resources are managed in Serverless mode. Computing and storage resources are used on demand in Serverless mode to avoid resource waste. Compute nodes are stateless. Scale-outs can be implemented without data migration. The SharedMergeTree table engine is available, which provides better scalability, supports scale-outs in seconds, and is compatible with the MergeTree engines. For more information, see SharedMergeTree table engine.
High availability	By default, high availability is enabled for ApsaraDB for ClickHouse Enterprise Edition. The number of compute nodes in a single cluster is greater than or equal to two. Data is shared among compute nodes.
Compatibility	In addition to new features, ApsaraDB for ClickHouse Enterprise Edition also supports some critical features of Community-compatible Edition. For more information, see Compatibility of ApsaraDB for ClickHouse Enterprise Edition.
Optimized performance	Parallel replicas are supported to linearly improve the concurrent processing capability of clusters. Lightweight updates and deletes are supported to allow you to query the execution results of the UPDATE and DELETE statements in real time. This also improves the execution efficiency. ClickHouse Keeper is supported and replaces ZooKeeper to deliver higher performance and reduce memory usage.


Enterprise-level O&M	The following enterprise-level O&M capabilities are supported: User management Whitelist configuration Version upgrade Failover Visualized O&M
Enterprise-level O&M
Data ecosystem	Enterprise Edition supports convenient data synchronization and migration with other data sources in the cloud.

Architecture of Community-compatible Edition

ApsaraDB for ClickHouse Community-compatible Edition integrates computing and storage resources and has the following characteristics:

For ApsaraDB for ClickHouse Community-compatible Edition, all nodes are peer nodes. Each node can compute and manage background data, and process query and write requests.
Each ApsaraDB for ClickHouse Community-compatible Edition cluster contains one or more shards. Each shard contains one or more replicas.
All nodes are deployed on Alibaba Cloud Elastic Compute Service (ECS) instances. At the underlying layer, highly reliable disks are used as the persistent storage.

总体架构图

Enhanced features

Feature	Description
Scalability	A variety of specifications and elastic scaling are supported.
Security	Security features such as user management and whitelists are supported.
Visualized O&M	Operations such as version upgrades and failovers are supported.
Data ecosystem	Community-compatible Edition supports convenient data synchronization and migration with other data sources in the cloud.

Engine versions

Category		Enterprise Edition	Community-compatible Edition
Category		Enterprise Edition	22.8	21.8	20.8	20.3	19.15
Engine	MaterializeMySQL (real-time data synchronization from MySQL)	❌	✔️	✔️	✔️	❌	❌
	MaxCompute external tables	❌	✔️	✔️	✔️	✔️	✔️
	OSS external tables	✔️	✔️	✔️	✔️	✔️	✔️
	Lightweight updates	✔️	❌	❌	❌	❌	❌
	Lightweight deletes	✔️	✔️	❌	❌	❌	❌
O&M	Cluster start and stop	✔️	❌	❌	❌	❌	❌
	Scaling range modification for Enterprise Edition	✔️	❌	❌	❌	❌	❌
	Parameter settings	❌	✔️	✔️	✔️	✔️	✔️
	Monitoring and management of slow SQL queries and running SQL queries	✔️	✔️	✔️	✔️	✔️	✔️
	Account management	✔️	✔️	✔️	✔️	✔️	✔️
	Cluster restart	✔️	✔️	✔️	✔️	✔️	✔️
	Scale-in and scale-out Note Enterprise Edition supports automatic scale-in and scale-out of resources.	✔️	✔️	✔️	✔️	✔️	✔️
	Scale-up and scale-down Note Enterprise Edition supports automatic scale-up and scale-down of resources.	✔️	✔️	✔️	✔️	✔️	✔️
	Backup and restoration	❌	✔️	✔️	❌	❌	❌
	Monitoring and alerting	✔️	✔️	✔️	✔️	✔️	✔️
	Minor engine version updates	✔️	✔️	✔️	❌	❌	❌
	Tiered storage of hot data and cold data Note Enterprise Edition automatically stores hot data in the cache and cold data in shared storage. Community-compatible Edition separately stores cold data and hot data based on specific storage rules.	✔️	✔️	✔️	✔️	❌	❌
	Data migration between ApsaraDB for ClickHouse clusters Note This feature has limits only on the version of destination clusters.	❌	✔️	✔️	✔️	❌	❌
	Data security	✔️	✔️	✔️	✔️	✔️	✔️

References

For more information about how to purchase a cluster, see Create an ApsaraDB for ClickHouse cluster.
For more information about how to migrate data from a self-managed ClickHouse cluster or a cluster of ApsaraDB for ClickHouse Community-compatible Edition to a cluster of ApsaraDB for ClickHouse Enterprise Edition, see Migrate data from a self-managed ClickHouse cluster to an ApsaraDB for ClickHouse Enterprise Edition cluster.