See Rockset
in action

Get a product tour with a Rockset engineer

SingleStore vs StarRocks

Compare and contrast SingleStore and StarRocks by architecture, ingestion, queries, performance, and scalability.

Compare SingleStore to Rockset here

Compare StarRocks to Rockset here

SingleStore vs StarRocks Architecture

Architecture
SingleStore
StarRocks
Deployment model
Self managed and SaaS deployment options
PaaS or self managed
Use of storage hierarchy
• Memory - for data requiring the highest performance • High-performance block storage for persistent cache - the working dataset should fit within the persistent cache • Cloud object storage for long-term retention
Data is stored on disk and in memory
Isolation of ingest and query
No - databases share ingest and queries
No, but you can limit resources for ingestion and querying separately
Separation of compute and storage
Yes - Singlestore Cloud uses cloud object storage for separation of compute and storage
No, but StarRocks supports nodes that don't store data locally
Isolation for multiple applications
No
No

SingleStore is a proprietary distributed relational database that handles both transactional and analytical workloads. It relies on memory and a persistent cache to deliver low latency queries. For longer term data retention, SingleStore Cloud separates compute from cloud object storage. SingleStore Cloud pricing is based on compute and storage usage.

StarRocks is a high-performance OLAP database that can be deployed on the cloud or self managed. StarRocks does not separate compute and storage and offers limited options for resource isolation. It offers a robust set of features and high performance but requires considerable expertise to operate and scale.

SingleStore vs StarRocks Ingestion

Ingestion
SingleStore
StarRocks
Data sources
Integrations to: Amazon S3, Apache Beam, GCS, HDFS, Kafka, Spark, Qlik Replicate, HVR
Streaming • Kafka • Flink Data lakes • HDFS compatible • Cloud storage
Semi structured data
Ingests JSON as a JSON column type
Supports columns with JSON data • Does not support mixed-type columns • Support for star and snowflake schemas
Transformations and rollups
SingleStore pipelines do common data shaping including normalizing and denormalizing data, adding computed columns, filtering data, mapping data, splitting records into multiple destination tables
Yes, via materialized views

SingleStore has integrations to common data lakes and streams. With SingleStore pipelines, users can perform common data transformations during the ingestion process. SingleStore provides limited support for semi-structured data with its JSON column type. Many users structure data prior to ingestion for optimal query performance.

StarRocks ingests data from a variety of sources, including both batch and streaming data. StarRocks can ingest nested JSON data, but enforces type at the column level.

See Rockset in action
Get a product tour with a Rockset engineer.
Get a demo

SingleStore vs StarRocks Performance

Performance
SingleStore
StarRocks
Updates
SingleStore columnar store/universal storage is immutable. Updates are fast when the data still resides in memory
While StarRocks is mutable, the update rate is slow, which is why it is most often used for append-only workloads
Indexing
Indexes can be manually configured: Skiplist index, hash index, full-text index, geospatial index
Columnar index, limited support for inverted indexes
Query latency
50-1000ms queries when the working set is contained in memory
50-1000ms queries on 100s of TB
Storage format
Two table formats-either use the rowstore or columnstore/universal storage
• StarRocks is a columnstore that organizes data into prefix indexes, per-column data blocks, and per-column indexes • All data is replicated 3 times to achieve both fault-tolerance and concurrency
Streaming ingest
• Columnnar store/universal storage ingests on a batch basis • Data latency is typically seconds by relying on memory
Data latency is typically 1-2 seconds

SingleStore has two storage formats: a rowstore and a columnar store referred to as universal storage. The columnar store is used for analytical workloads, loading data in batch and relying on memory to achieve seconds of data latency. The columnar store can also execute queries in seconds when the working set is contained in memory. SingleStore provides the ability to configure and manage additional indexes on the data for faster performance.

StarRocks was purpose-built for high-performance ingest, low-latency queries, and high concurrency. Optimized performance requires significant manual tuning.

SingleStore vs StarRocks Queries

Queries
SingleStore
StarRocks
Joins
Yes
Multi-table join support
Query language
SQL
SQL
Developer tooling
• API for querying data via POST command • JDBC driver, Python client • Compatibility with MySQL and MariaDB to support additional drivers
Minimal
Visualization tools
Integrations with Cognos Analytics, Dremio, Looker, Microstrategy, Power BI, Sisense, Tableau and Tibco Spotfire
Compatibility with MySQL protocols enables StarRocks to work with BI tools

SingleStore supports SQL as its native query language and can perform SQL joins. It is designed for querying structured data with static schemas. Users can create data APIs to execute SQL statements against the database over an HTTP connection. Common SingleStore use cases include business intelligence and analytics, and the database offers a number of integrations to visualization tools.

StarRocks uses a high-performance vectorized SQL engine, a custom-built cost-based optimizer, and has support for materialized views.

SingleStore vs StarRocks Scalability

Scalability
SingleStore
StarRocks
Vertical scaling
• Cloud offering: Resize compute workspaces in the UI or using the Management API • Self-managed offering: Change cluster configuration by updating command-line arguments or to the cluster directly.
• Both frontend and backend nodes can be manually resized
Horizontal scaling
Self-managed offering: Increase or decrease the number of nodes in the cluster. Rebalancing required
• Both frontend and backend nodes can be manually scaled horizontally

SingleStore Cloud can be sized up or down using the UI or the Management API. There is no ability to scale out by increasing or decreasing the leaf and aggregator nodes in the cloud offering. In the self-managed offering, horizontal and vertical scaling can occur by updating command-line arguments or the cluster directly. Horizontal scaling does require rebalancing

StarRocks can scale up or out, but its tightly coupled compute and storage scale together for performance. This often results in resource contention and overprovisioning. Scaling StarRocks often requires deep expertise as there are many levels of the system that need to be managed.

See Rockset in action
Sub-second SQL on streaming data with surprising efficiency.
Get a demo