SingleStore Managed Service

Cluster Components

Key Components

The following components are fundamental to a SingleStore cluster. They are also key terms that are used throughout the documentation.


A cluster encompasses all of the nodes that are included in a complete SingleStore DB installation.


A node is a server that has an installation of a SingleStore instance.


A partition contains a subset (a shard) of a database’s data. A node contains multiple partitions. When you run CREATE DATABASE, SingleStore splits the database into partitions, which are distributed evenly among available nodes. With CREATE DATABASE, you can specify the number of partitions with the PARTITIONS=X option.


SingleStore stores data in tables, which can be of one of the following types:

  • Universal Storage - (Default) Supports large-scale Online Transaction Processing (OLTP) and Hybrid Transactional and Analytical Processing (HTAP) workloads at a lower total cost of ownership (TCO). Universal Storage is a continuing evolution of the columnstore and supports transactional workloads that would have traditionally used the rowstore. SingleStore recommends using the Universal Storage tables for all kinds of workloads.

  • Rowstore - In-memory rowstore tables for high-performance OLTP workloads.

The tables can have the following properties:

  • Sharded or Reference - A sharded table’s data is distributed across partitions. By contrast, a reference table’s data is replicated, in full, to all nodes in a cluster.

  • Persisted or Temporary - Defines whether the data stored in a table is persisted or stored temporarily for the duration of a client session. Temporary tables can further be classified into regular temporary tables and global temporary tables.