TrustRadius Insights for SingleStore are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Real-Time Data Processing Capabilities: Users have consistently praised SingleStore for its efficient real-time data processing capabilities, noting its effectiveness in online transaction processing and big-data batch handling. The seamless integration with external services like Kafka and S3 has also been highlighted as a significant advantage.
Super Fast Data Queries: Reviewers have emphasized the exceptional speed of data queries on SingleStore, enabling them to quickly and efficiently retrieve information for their needs. This feature is seen as a key benefit that enhances overall productivity and decision-making processes.
Scalability and Performance Improvements: Users appreciate SingleStore's scalability for both writes and reads, along with notable performance enhancements. These include faster request processing rates, improved algorithm processing times, and the ability to handle growing workloads without compromising efficiency or reliability.
We use SingleStore for real time analytics (primarily for dynamic and transactional data). We have row store used for fast compute and streaming data and column store for more historic data fetch. Use case is to stage data from different domains within enterprise in real time streaming (kafka) and compute/apply algorithm on the dynamic data across enterprise for quick decisions.
Pros
Real time computations on large sets of data
Persisting streaming data
Data distributions and fast fetch
Cons
Semantic layer can be better, currently requires significant dev experience to fine tune queries
Query performance dashboard and self optimization methods instead of relying on keys
Bootstrap AI models to help provide recommendations as the user gets into UI (back to semantic)
Likelihood to Recommend
It is extremely good for scenarios where large sets of data is generated in a day and data is streamed. Especially if you would like to run queries, analytics on such data it would really scale and outperform Times DB or Oracle In memory options. But choosing this tech for right use case is key, should avoid using SingleStore like a ER DB and for that there are so many options in the market like Postgres or Oracle lite etc.
VU
Verified User
Employee in Information Technology (Information Technology & Services company, 10,001+ employees)
We use SingleStore for a super fast client experience, running real time analytics on billions of events arriving every day from various publishers channels.
Pros
Performance - Milliseconds response of 80 tables Joined queries
Scalability - Ability to grow with no downtimes
Client success - Attentive to business needs, deep level support, patches and fixes
Efficiency - Built-in Kafka / S3 / MySQL integrations well adjusted to leverage SingleStore architecture and hardware
.
.
.
.
.
Cons
Add Iceberg tables / files Pipeline
CDC out in form of logfile / binlog / producer to Kafka
Efficiency with multi shard-key use case: Joined three tables when one of them holds both shard keys of the other two.
.
.
.
Likelihood to Recommend
SingleStore shines as a unified solution of high OLTP & OLAP workloads. The technology suits big data systems with mutual identity (shard key/s), fast JSON processing, vector search for AI features and streaming.
The client success attentiveness and the consistent support of experts in any matter shows the company maturity and their vision for success. No doubt this is a long term partnership.
SingleStore is being used for concurrent high performance reporting powering Tableau BOBJ PowerBI and conventional .net and java pages. It is also being used for real time reporting with data loaded from OLTP systems using GoldenGate, Kafka and Spark. SingleStore is being used in Sales, Finance, Supply Chain, Inventory Management, Marketing, Servicing and Logistics reporting.
Pros
Powering multiple dashboards on a single screen within short span of time
Real time reporting for IOT devices
Warehouse queries powering dashboards which suffers due to concurrency in Warehouse Database Systems
Cons
Auto failover to DR Site
Eventual Consistency
Point in time recovery
Robust Monitoring
Likelihood to Recommend
SingleStore is well suited for warehouse dashboards used at executive level. There is no latency due to concurrency and the performance is terrific compared to SingleNode traditional databases.
High speed data ingestion powering IOT and other workload which also needs high speed seeks.
SingleStore support as well as Marketing team is excellent. They are always with you to troubleshoot until we achieve a fix.
Where SingleStore lacks is in OLTP systems where there is no capability of PITR. It is more like Flashback. Monitoring is still not robust, they provide exporter that can be used in Prometheus for alerting, but no monitoring rules are directly provided by SingleStore. Grafana prebuilt dashboard is provided which is good.
VU
Verified User
Administrator in Information Technology (Information Technology & Services company, 10,001+ employees)
SingleStore has allowed us to simplify our analytical queries. It has allowed us to eliminate intensive jobs that compiled stats for the previous day and instead given us a way to run those same queries on demand eliminating discrepancies and giving our organization the ability to tackle any analysis without having worry about it impacting other aspects of our stack.
Pros
Statistical analysis
Data ingestion
S3 integration
Cons
Schema altering
Lucene engine column compatibility
Use as a primary transactional db
Likelihood to Recommend
If analytical workloads are necessary this solves many problems and is a viable solution. It has lots of ways to ingest and export. Its not suitable as a heavy traffic transactional db, but as a piggy back it is ideal. It has been very reliable to boot, we love it!
VU
Verified User
Engineer in Engineering (Marketing & Advertising company, 11-50 employees)
We use a single store for an analytics use case in our organization. The previous database was not distributed, and scaling issues were occurring, so a single store with a distributed nature helped us solve this issue. We mainly use the columnar tables in a single store for analytics.
Pros
Sharding/Distributed Database.
Analytics Queries.
Good Observability.
Cons
Row tables.
Query Profiler.
Likelihood to Recommend
In my opinion, it is well suited for analytics use cases. However, it is less appropriate for transactional data as row tables are saved in memory, and single nodes are more costly than traditional databases.
VU
Verified User
Engineer in Engineering (Information Technology & Services company, 1001-5000 employees)
Singlestore powers everything for us. It is our entire dataware house and powers all of our main business functions. All of our business analytics related to customers, churn, retention. We use it for all of our data ingest which is hundreds of gb per day and it handles all of that nicely. We power our frontend app which displays all kinds of data. Timeseries, AI, etc.
Pros
Data Ingestion
Scaling Compute
OLTP and OLAP queries
Cons
Pipeline Monitoring
Data Migration Tooling
Multiple SQL editors with AI completion in web UI
Likelihood to Recommend
If you are doing data larger than normal app data (I.e. 1 - 2 mb / day) Singlestore is great and can scale with you as you grow.
Maybe if you're data isn't growing constantly you could get away with another solution.
VU
Verified User
Engineer in Engineering (Information Technology & Services company, 11-50 employees)
We recommend SingleStore to our customers who face scalability issues with their OLTP or OLAP systems. Many companies use database engines that are inappropriate for specific data computing tasks. For example, MySQL is not meant for analytics or real-time analytics. SingleStore is. SingleStore compresses data, which lowers your disk footprint, thus saving storage costs. Most of the time, we'll do a discovery about our customer pain points and determine if SingleStore is the right fit. We'll then work with SingleStore to do a POC to ensure we meet all customer requirements.
Pros
Data Ingestion
Scaling Writes and Reads
Compressing Data
Support
Short learning curve
Cons
Mysql to SingleStore replication
Likelihood to Recommend
SingleStore HTAP engine is well suited for real-time analytics, fast ingestion, scaling OLTP system like MySQL. When you need to run reports or perform aggregates on billions of rows and you get result in seconds, you cannot get this experience with other OLTP engines. I wish DBtLab was a little more developer and supported for SingleStore. This would allow to perform better data transformation. You can use stored procedures, but DBTLabs has become a standard for dimensional modeling in data warehousing projects. This is probably why SingleStore has trouble piercing in the data warehouse world. It is definately capable to compete with Snowflake when it comes to scalability, query performance, data compression, but Snowflake has ravaged the data warehouse market in few years and large corporations have already invested lots of money in migrating into Snowflake. The SingleStore community needs to grow. Everyone who uses SingleStore loves it.
We use SingleStore for our various web apps. We were previously using AWS RDS which was slowing things down as we added more data and added more analytics, queries, and data enrichment tasks. Moving to SingleStore removed all of those bottlenecks.
Pros
Performance - from 60 to 1,000 requests/min
Scalability - grows as we grow
Processing - predictive algorithms went from taking 48 hrs down to 15 min
Customer Service - monthly touchpoints
Cons
SSO integration was initially challenging - they are already improving this
Cost - each tier literally doubles in price. It would be nice if there was some discounting as you go up.
Likelihood to Recommend
Business analytics is one of the areas where SingleStore really helped. As we implemented BI platforms, the previous DB would bog down so bad that it negatively affected our online products. Moving to SingleStore made a huge difference. General performance is amazing. We gained speed in areas we were not even expecting to the point we had to slow down or put rate limits in place to avoid duplications - something completely unexpected. The hosted service is great. We no longer have to worry about maintenance, db infrastructure or system updates which saves a significant amount of time for the IT team.
VU
Verified User
Engineer in Information Technology (Marketing & Advertising company, 11-50 employees)
We use it as our analytical database. It is more reliable and faster than our previous vendor. It also allowed us to replace another service that frees up $1500/month. We retrieve thousands of records at a time quickly.
Pros
Delivering thousands of records at blazing fast speeds
full text search
scaling
Cons
Improved UI for their portal
Better ticket system
More workers on workspace
Likelihood to Recommend
Reliable, scales and you can do full text search across the data. Customer support ticketing system could be improved but it's barely a con
VU
Verified User
Team Lead in Engineering (Research company, 51-200 employees)
My team and I have engaged with SingleStore, discussing the potential use of their database in our newly developed application. In collaboration with the SingleStore team, we conducted a POC to show the advantages of using SingleStore in our application.
Pros
high query speed
vector databases
transactional and analytical database in one
Cons
head to head comparison with the competition
Simplification of the ETL process
Integration with more BI platforms.
Likelihood to Recommend
SingleStore is suitable when using transactional and analytical databases in one. SingleStore is highly scalable for new applications where they start small while planning for a large future growth.