Differences between Klustron Database Professional Edition and Enterprise Edition
Differences between Klustron Database Professional Edition and Enterprise Edition
Starting from Klustron-1.4 version, Klustron has added a Professional Edition, which is formed by limiting the features and resource quantities of the Enterprise Edition, intended for trial use and small-scale commercial users. Specifically, we have imposed the following restrictions on the Professional Edition features. Users who need larger scale, higher load, higher reliability, and advanced features need to purchase an Enterprise Edition license to unlock all features.
Maximum of 10 LOGIN users can be created, i.e., users for login.
User creation statement: CREATE USER abc WITH LOGIN
Each user can initiate a maximum of 50 connections. If CONNECTION LIMIT greater than 50 is specified when creating a user with CREATE USER, it will be set to 50.
Each compute node accepts a maximum of 100 connections, and the total number of connections from sessions in all compute nodes to each storage node is also a maximum of 100.
The internal state in the compute node corresponding to each client connection is also called a session. Each session initiates exclusive backend connections to storage nodes to read and write data. These restrictions mean that if a cluster has two compute nodes and two shards, when the total number of connections to the two compute nodes reaches 50, the total number of backend connections belonging to these 50 sessions may have already reached 100, or some of the sessions may only be connected to 1 shard, thus leaving some backend connection quota available for more sessions.
Maximum of 10 databases can be created, and the total number of all schemas in all databases does not exceed 20.
The maximum connection limit for each database is 50.
If a CONNECTION LIMIT greater than 50 is set in the CREATE DATABASE statement, the actual effective value is 50.
The cluster has a maximum of two compute nodes, and the cluster can use a maximum of two storage shards.
Each storage shard has at most two standby nodes, and its fullsync_consistency_level can only be set to 1.
Klustron Enterprise Edition supports up to 6 standby nodes per shard, and fullsync_consistency_level can be set to the total number of standby nodes to achieve extremely high availability and fault tolerance.
The number of concurrent connections from concurrent queries to each storage node is no more than 3.
The following advanced feature components are not available: Kunlun-postgis, Kunlun-pgml, Kunlun-pgvector, Kunlun-sql_firewall, tornado, etc.
