Skip to content

16.6.1 Feature Support by Edition

Machbase provides Standard Edition for a single server and Cluster Edition for horizontal scaling across nodes. They share core time-series features, but supported features differ according to scalability and high availability requirements.

Feature Comparison

FeatureStandardClusterNotes
Table Types
TAG tablesOO
LOG tablesOO
LOOKUP tablesOO
TRANSACTION tablesOXNot supported in Cluster Edition
VOLATILE tablesOOCheck the node and restart lifecycle of in-memory data in your deployment
Data Management
ROLLUP (basic)OO
Custom ROLLUPOXNot supported in Cluster Edition
ROLLUP_REBUILDOXNot supported in Cluster Edition
Backup and Recovery
Multiple logical databasesOXStandard Edition only. No physical CPU, memory, or disk quotas per database
BACKUP DATABASEOO
BACKUP TABLEOO
MOUNT DATABASEOXNot supported in Cluster Edition
UMOUNT DATABASEOXNot supported in Cluster Edition
machadmin -r restoreOXNot supported in Cluster Edition
Scalability and HA
Horizontal scalingXOScale by adding Warehouse nodes
HA (high availability)XOBroker/Warehouse redundancy
AUTH KEY authenticationOO

Cluster Edition Constraints

Cluster Edition has constraints on local file operations centered on a single node and on TRANSACTION features.

  • TRANSACTION tables: TRANSACTION tables providing ACID transactions are not supported in the distributed environment. Integrate with an external RDBMS for data requiring transactions.
  • VOLATILE tables: Creation and DML are supported, but in-memory data is local to each node and is not shared across nodes. Verify data visibility with the connected Broker, routing, and node restarts.
  • MOUNT/UMOUNT: Local filesystem backup mounts are not supported in the distributed environment.
  • Custom ROLLUP / ROLLUP_REBUILD: Custom rollup redefinition and rebuilding are not supported because the distributed aggregation architecture differs.

Choosing an Edition

RequirementRecommended Edition
Workload within one server’s throughput and storage capacityStandard Edition
Workload requiring horizontal scaling beyond one serverCluster Edition
High availability with automatic failure recoveryCluster Edition
TRANSACTION tables or MOUNTStandard Edition
Real-time ingestion exceeds one server’s capacity and requires more nodesCluster Edition
Last updated on