Skip to main content
TrustRadius
SingleStore

SingleStore
Formerly MemSQL

Overview

What is SingleStore?

SingleStore aims to enable organizations to scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.

Read more

Learn from top reviewers

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing

OnDemand

$0.69

Cloud
per hour

Entry-level set up fee?

  • Setup fee optional
For the latest information on pricing, visithttps://www.singlestore.com/pricing/

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is SingleStore?

SingleStore enables organizations to quickly and easily scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.

SingleStore Features

  • Supported: Vector database
  • Supported: Transactions (OLTP)
  • Supported: Analytics (OLAP)
  • Supported: SQL
  • Supported: JSON
  • Supported: Real-time

SingleStore Videos

SingleStore NOW 2024: Outreach / AI- and Data-Driven Sales
SingleStore Now 2024 / Snowflake + SingleStore: Better Together
SingleStore NOW 2024: Adobe / What’s New in SingleStore: AI in Production
SingleStore Now 2024: AWS / Enterprise AI Innovation: Gen AI Experimentation
SingleStore Now 2024: 6sense / AI in Production: Lessons Learned
SingleStore Now 2024: LlamaIndex / Building Multi-Agent RAG Systems
SingleStore NOW 2024 / LiveRamp: Building the World’s Largest Identity Graph without a Graph DB
SingleStore Now 2024: SAS + SingleStore = Enterprise AI at Scale
SingleStore Now 2024 / Pyler: AI-Powered Brand Safety
SingleStore Now 2024: Groq / AI Trends, and Running LLMs in the Enterprise
SingleStore Now 2024: AI with SingleStore, IBM StreamSets and watsonx.ai

SingleStore Integrations

SingleStore Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsLinux
Mobile ApplicationNo
Supported CountriesGlobal
Supported LanguagesEnglish

Frequently Asked Questions

SingleStore aims to enable organizations to scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.

Oracle Database, Microsoft SQL Server, and MongoDB are common alternatives for SingleStore.

Reviewers rate Performance highest, with a score of 9.2.

The most common users of SingleStore are from Small Businesses (1-50 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-5 of 52)

Scale the DB without scaling your engineers

Rating: 8 out of 10
June 12, 2021
Vetted Review
Verified User
SingleStore
4 years of experience
We use it as the core database for our entire IoT platform and for all our customers.
  • We use it as a replacement for having a separate in-memory cache and a traditional disk-based database because SingleStore does both in a single package.
  • We also use the row store for storing transactional state and the column store for storing time series data. Having both in the same product is nice.
  • We get 7x compression for the time series data, which is really good for scaling.
Cons
  • We wish the product had better support for High Availability of the aggregator. Currently the indexes generated by the two different aggregators are not in the same sequential space and so our apps have more burden to deal with HA.
  • More tools for debugging issues such as high memory usage would be good.
  • The price was the one that kept us away from purchasing for the first few years. Now we are able to afford due to a promotion that gives it at 25% of the list price. Not sure if we'll continue after the promotion offer expires in another 2 years.
It's great to have a scalable story rather than spending time doing your own clustering with a bunch of MySQL servers.

SingleStore computing data at scale

Rating: 9 out of 10
August 26, 2021
EG
Vetted Review
Verified User
SingleStore
2 years of experience
We are proud to say that SKAI is a data company and our main asset is our data. My department handles the Measurements data and other incoming data sources. SingleStore is used across the organization to do real-time calculations, supply fast loading grids and store massive amounts of data. In our department, users needed to configure pre-hand MetaData for the calculations that they are basing their decision on. Our nightly batches used to work extremely hard and waste valuable time and resources to make this data available the next day (while storing it both in raw form and aggregated) and any changes required a rerun of the batch. Today the clients can configure, change and get their aggregated data in almost real-time, while the data is being stored in SingleStore only in its raw form. It allowed us to add more calculations and more data and use fewer resources on our server-side and the added bonus is that our clients love it!
  • Real-time calculation.
  • Massive data storage.
  • Real-time updates and integration.
Cons
  • Scaling up (adding memory) takes a lot of time.
  • Real-time information about lags is limited.
If you need real-time calculation and reduce DB lags in production it's ideal.

If you're looking only for storage, I would pass.

Robust, Fast, and Scalable Database Solution

Rating: 9 out of 10
June 06, 2024
NL
Vetted Review
Verified User
SingleStore
1 year of experience
We are using SingleStore database as our main database in both production and non-production workloads. We are using both memory-based tables and disc-based tables (AKA column-store) and can easily join and query all tables. Our use of SingleStore is for many diverse business use cases, ranging from online data streaming, OLTP, and big-data batch processing.
SingleStore proved to be an excellent business and technical partner, with a top-of-line technical product and good business and technical support. Support is provided either directly from the supplier or from SingleStore's trusted partners
  • Real-time data processing
  • Online transaction processing
  • Big-data batch handling
  • Integration with external services (Kafka, S3, etc.)
  • Super fast data queries
Cons
  • While improving, backup is still hard to configure
  • Pricing of self-hosted instances
  • Few external documentation resources
I would recommend SingleStore for use cases where a relational database is needed for handling both online transaction processing (OLTP), online data streaming, and batch big-data processing. Since it supports both in-memory and disc-based tables, it is suitable for handling large tables as well as smaller, fast ones.
SingleStore is MySQL compatible in terms of connection so you could use it with any connector that supports MySQL, and is mostly TSQL compatible so if you come from Transact-SQL background the switch will be simple.
While supporting JSON and document datatypes, I would not use SingleStore as a main document database, as its strengths lay in the relational realm.

Maximum performance and scalability in one.

Rating: 9 out of 10
December 15, 2020
JO
Vetted Review
Verified User
SingleStore
1 year of experience
Right now we’re using [SingleStore (formerly MemSQL)] in the whole core platform, we were looking for a database that could handle a huge amount of transactions at the same time without loosing any and have the reliability of writing and storing the records fast so other services can use the data for finalizing the transactions. Also we were aiming to have a product which could be used as a storage solution for Data Scientists and our back office platform.
  • The fastest speed for querying compared with traditional relational database
  • Support JSON and full text search which can be used by API’s
  • Nearly zero admin tasks once it’s running
  • You can use it’s data streaming pipeline with Kafka
Cons
  • It doesn’t provide redistribution when you reach the maximum node capacity
  • The Graphical Interface could have a revamp, it’s a little bit laggy
  • You cannot run it local so development should be made always using cloud instances
I think SingleStore [(formerly MemSQL)] should be used in every modern system which needs an analytical tool provided with the database, where performance matters and when you need fast scaling. The database is going to use a lot of resources so if the scenario is cost sensitive then perhaps is not the best solution in terms of infrastructure.

Best in-memory scale out engine on the market for wealthy customers

Rating: 8 out of 10
December 04, 2020
Vetted Review
Verified User
SingleStore
3 years of experience
We use [SingleStore] [(formerly MemSQL)] to address the ingestion of fast data streams and to answer analytical queries with tight timeout requirement.
  • Fast analytical queries with in-mem and on-disk columnar store.
  • Scale out capability
  • Good dashboard for managing the cluster
Cons
  • Licencing model needs to be more flexible, users need to be able to do pay-as-you-go
  • Data ingestion is still old-style. Integration with e.g., spark lagged behind.
  • In-mem and col-store does not share the same language compat. Table type transition is hard.
  • HA is no good with 6.0. Recovery time is very long. (and non-predictable)
[SingleStore (formerly MemSQL)] is a good OLAP scale-out system with mysql compat. for rich customers. Suitable for fast analytical queries.
The single-main arch. (with read-only backup) limits it's OLTP concurrency as well as the OLAP query throughput.

Good to build small to medium sized (near) real-time analytical systems with. The cost and inflexible licensing model limits large scaled use.
Technically the best in-mem distributed RDBMS in class.

Management-wise although the dashboard and studio is a good start, to make it a 24-7 reliable database system there is still room to improve.
HA cost is very high as it also eats the licensed mem-space. The costly mem-based table and free on-disk columnar tables don't automatically play will together. E.g., auto offloading old data from in-men to on-disk is not supported, making it hard for DBA to manage the cluster.
Return to navigation