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.
Loading Reviews List....
SingleStore Reviews
32 Reviews
Small Businesses (1-50 employees)
Search is temporarily unavailable. Filters are still applied.
IOT data processing and log analysis. The power of unified management is evident out of the box. Quick deployment, comprehensive troubleshooting, and customizable periodic reports increase productivity with fewer resources. Streamline, optimize, and elevate the network management experience through a single pane of glass with organization hierarchy, access controls, alerts from security threats, and usage thresholds - solutions that simplify network fabric and prioritize results to improve efficiency.
Pros
Can scale horizontally on cloud instances.
Can analyze large volumes of time-series data in real time.
Can perform queries in milliseconds.
Can process large amounts of data in parallel.
Cons
Can be expensive for small startups.
Migrating from traditional databases e.g., MySQL, PostgreSQL is complex.
Switching to another database might require significant re-engineering.
Likelihood to Recommend
Good for Applications needing instant insights on large, streaming datasets. Applications processing continuous data streams with low latency. When a multi-cloud, high-availability database is required When NOT to Use Small-scale applications with limited budgets Projects that do not require real-time analytics or distributed scaling Teams without experience in distributed databases and HTAP architectures.
VU
Verified User
Employee in Information Technology (11-50 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!
We use SingleStore for database storage and management and SingleStore addresses mainly performance issues we had with Azure in the past. SingleStore is much quicker and timelier. It helps reduce latency and customer kickback with their efficient load times and just an overall smoother user experience and user interface for all.
Pros
Performance
Data fluidity
Great customer support
Cons
Backup times
simplifying data management
expediting load processes
Likelihood to Recommend
SingleStore is well-suited for applications such as ours at dailyVest require real-time analytics, high-performance transactions, and large-scale data processing due to its distributed architecture, in-memory processing capabilities, and ability to handle both transactional and analytical workloads simultaneously.
VU
Verified User
Project Manager in Information Technology (1-10 employees)
SingleStore is our main database. We use it to serve our application including user and account information as well as millions and millions of rows of data that we gather every day. SingleStore has enabled us to only need one storage solution which simplifies our processes a lot. It has also enabled us to do very complex and computational intense queries on the fly to serve up results to our customers.
Pros
Ingesting large amounts of data relatively fast using pipelines.
Runs large/intense data analytical queries very fast and efficient.
Free Tier is nice to get started.
Cons
Customer Service tickets take way to long to get responses when something critical is breaking.
Pricing can at times be a bit unclear.
Pipelines are great but can be a bit of a black box.
Likelihood to Recommend
If you need 1 database to handle all your use cases SingleStore works great. Enabling you to store user/account information on the same database as analytical time-series data is game changing. If you don't have large amounts of data that you need to run very fast analytical queries then SingleStore is probably a bit overkill for your use case.
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.
SingleStore is our only database solution we currently use. It is used at the application level to serve and store user information. We are a data company and serve up millions and millions of datapoints to customers and all that data is stored in SingleStore. SingleStore enables us to do quick analytical queries on millions of rows of data in seconds allowing us to be a market leader in the data space.
Pros
Efficiency
Reliability
Speed
Cons
Customer Service
Likelihood to Recommend
If multiple terabytes of data are involved and analytical queries are required on all of the data then SingleStore is a great option. We have tried other database providers and they were unable to handle the amount of data in a fast enough manner to serve up an application. However we have had issues with customer service resolving issues that were causing us problems on our end.
We are using SingleStore to power our whole app database layer. We use it both for our basic tables and also for the analytical ones.
The magic is that we don't need to have multiple types of databases, it's just a single database which is a drop-in replacement for MySQL and it works almost exactly the same at the API level with some differences, which we can live with but hope they can improve upon (like column adjustments on the fly, foreign keys, etc.)
Pros
Analytical queries
Basic SQL usage similar to how you would use MySQL
Cons
Column mutations (from null to not null, or type changes)
Foreign keys
Unique columns (for columnstore)
Likelihood to Recommend
It's perfect if you don't want to juggle multiple database providers for analytical and other app data. Also, it's great that it's managed.
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 to ingest, store, and process data from our hardware player trackers. The challenge is the amount of data (hundreds of millions of rows) and being able to query it quickly.
Pros
Fast ingest via Pipelines
Standard SQL syntax
Fast query times
Cons
The dashboard should show a list of recent backups (you have to run a query to get this information right now)
Likelihood to Recommend
SingleStore is well suited to handling tables with huge numbers of rows and being able to query these. It does its own thing with auto-incremented primary keys, so it may be difficult to migrate legacy MySQL applications with large numbers of tables.
