Migrate from Rockset to SingleStore

Ingestion for Data Sources

Rockset supports ingestion from a variety of data sources including streaming services, databases, and object stores. SingleStore supports most of the sources supported by Rockset along with additional sources. SingleStore provides native high-speed ingestion with pipelines, which support one-time loads up to massively-parallel incremental updates.

Partner integration solutions for:

• Azure Event Hubs

• Microsoft SQL Server

• Oracle

• PostgreSQL

Ingest Transformation

Rockset transforms data during ingestion. SingleStore supports data transformation through SQL-based procedures, which can effectively achieve the same behavior. These transformations are applied to both the initial data load and to new data that is ingested into SingleStore.

Collections

A set of Rockset documents is a collection, which is similar to tables in a relational database like SingleStore. Rockset allows querying this data either via SQL or through Query Lambdas. Similarly, SingleStore allows the data stored in relational tables to be queried via SQL, SingleStore Kai (for MongoDB® data sources), or a Data API that allows HTTP API access to SingleStore databases.

Aliases

Aliases are used to associate multiple names with Rockset collections, which is a concept that  SingleStore does not support.

Views

Views are virtual collections defined by SQL queries. A view’s SQL query may reference nothing, or may reference other views, collections, or aliases. SingleStore also supports views.

Workspaces

Workspaces are containers that hold Rockset resources such as collections, Query Lambdas, views, aliases,  and even other workspaces. SingleStore has a highly advanced version of workspaces that are elastic, with support for auto-scaling, and that provide complete role-based access control (RBAC), security, and isolation. Workspaces in SingleStore can be created from either a UI or via the Management API.

Refer to Rockset vs. SingleStore for a comprehensive technical comparison between these two platforms.

Full-Text Search

Rockset supports text search as part of its product offering, and provides full-text search via the SEARCH function. SingleStore not only matches these features but provides much richer search functionality with support for Java-based Lucene full-text search with the recent release of SingleStore v8.7.

Vector Search

Rockset added support for vector search using a similarity index, which is used for indexing the embeddings. However, there is no choice of indexing algorithm, which is an IVF_PQ index with support for dot, cosine, and Euclidean distance metrics.

SingleStore supports vector indexing with advanced algorithms like HSNW and IVF_PQ, and you can combine indexed vector search with full-text indexing. You can also combine vector search with queries over other data types, including JSON, time-series, full-text, spatial, and key-value data. SingleStore includes both exact K Nearest Neighbor (KNN) and indexed Approximate Nearest Neighbor (ANN). Provided distance metrics include dot product and Euclidean distance.

• Vector search

• Enhanced full text search

• Hybrid search

• Vector range search

JSON Data Support

JSON-based storage and query execution capabilities and compatibility with MySQL queries make it easy to migrate and translate Rockset queries over to SingleStore.

SingleStore provides a rich set of capabilities in JSON data processing for analytics and excels at delivering analytics on immense volumes of data, as evidenced by the performance of SingleStore Kai.

SingleStore supports seekable columnstore (universal storage) and columngroup indexes to allow combined row and columnar access to large tables. Indexes can be added to increase query performance and text indexes added on the JSON column to match for query strings over any field on JSON data.

SingleStore supports MySQL-style queries on JSON data which helps ease the migration of Rockset queries into SingleStore, thereby allowing further access to the MySQL ecosystem and MySQL-based tooling.

Transactions

Rockset is not a transactional database and is not designed to support OLTP workloads. Rockset provides atomic writes at the document level. While multiple fields can be updated atomically within a single document, atomic updates to more than one document are not supported. All writes are asynchronous, where the period from when data is written to the database to when the data is visible to queries varies between 1 and 5 seconds, which affects real-time responsiveness.

Conversely, SingleStore is an ACID-compliant database with support for transactions. Consolidating the entire data stack while providing  analytics on the same data storage is achievable.