The issue we encountered was the inability to efficiently extract and evaluate our data from existing databases, causing limitations with Tableau, which struggled to handle datasets exceeding a hundred million records. Consequently, we explored alternative systems and initially attempted to access all data from target systems. In pursuit of faster and more effective data management, we considered Exasol as an alternative OLAP system. Ultimately, we opted for SingleStore.
SingleStore Helios
SingleStoreExternal reviews
External reviews are not included in the AWS star rating for the product.
High-speed data processing, seamless scalability, and excellent high availability making it an optimal choice for those prioritizing performance and efficiency in a database solution
What is our primary use case?
What is most valuable?
The paramount advantage is the exceptional speed. Another noteworthy aspect of our experience is that, upon its setup, there aren't any issues that necessitate the intervention of a DBA. In terms of performance, it has proven impressive, particularly in handling complex joins without the need for data shortening. It excels in executing complex SQL operations swiftly.
What needs improvement?
There's a noteworthy consideration when it comes to collecting massive amounts of data. It is not the optimal choice for direct data collection through queries, and it's more suited for aggregation tasks. Attempting to use it for direct extraction, for instance, might lead to memory-related challenges. While MySQL version five might lack extensive SQL capabilities, SingleStore also has its constraints, requiring simpler SQL writing. This becomes evident when seeking advanced functionalities like window functions or JSON functions, where SingleStore doesn't offer an extensive toolkit, necessitating a more straightforward approach to SQL.
For how long have I used the solution?
We have used it for two years.
What do I think about the stability of the solution?
I would rate its stability capabilities ten out of ten.
What do I think about the scalability of the solution?
Regarding scalability, we did encounter occasional challenges as our data grew larger, resulting in potential out-of-memory issues. The resolution to this depends on the budget allocated. If budget constraints are not a concern, opting for a SaaS system is a viable solution, albeit with associated costs. Scaling the system incurs expenses for each additional node. I would rate it seven out of ten.
Which solution did I use previously and why did I switch?
I use Exasol, and it has proven to be highly effective. However, when considering factors such as cost, financial aspects, SQL version capabilities, and insertion times, there are certain drawbacks. Specifically, the performance in terms of insertion times is notably subpar.
How was the initial setup?
The initial setup was straightforward.
What about the implementation team?
The deployment process was remarkably swift, taking only one or two days, and we encountered no issues throughout the entire setup.
What other advice do I have?
If simplicity, quick data insertion, minimal complexity, and high availability are your primary concerns, and budget constraints aren't a major issue, then SingleStore is an excellent choice. I would rate it eight out of ten.
Can automatically reinstall and reconfigure in case of a shutdown
What is most valuable?
The product can automatically reinstall and reconfigure in case of a shutdown.
What needs improvement?
We don't get good discounts in Pakistan.
For how long have I used the solution?
I have been working with the product for three months.
What do I think about the stability of the solution?
I would rate the product's stability a nine out of ten.
What do I think about the scalability of the solution?
I would rate the solution's scalability a ten out of ten.
How was the initial setup?
SingleStore's setup is difficult.
What's my experience with pricing, setup cost, and licensing?
The product's licensing is not expensive. It is comparable.
What other advice do I have?
I would rate SingleStore a ten out of ten.
Wicked fast and easy to use database
The Best All-in-One Database Solution
Every other solution I looked at required me to maintain 2 seperate databases, certainly not ideal in any means..
Singlestore Power of Analytics
Great product for streaming data!
10X faster than MySQL, Postgres, Oracle and 1/4 the cost
Mysql - singlestore is super fast compared to this and infrastructure upgrades are no more a pain here due to Devops enabled for rapid deployment
postgresql - singlestore has Better Performance due to the possibility of running highly concurrent workloads. Also real time insights are possible in singlestore
Oracle - singlestore is 10*faster than oracle and also is 1/4th cost of oracle
Amazing Capabilities with this Product
Super fast for real-time big data analytics
High performance database ingestion for OLTP and OLAP
- UI is minimal and slick. Mostly, I have used SSMS and Visual studio to access the databases.
There will be lot of options in SSMS/Visual studio but we wont be using most of them and it will be confusing. I like SingleStore's minimal UI.
- UI options are easy to understand and navigate.
- Setting up a cluster with S-16, 128 vCPU and 1 TB RAM took less than 3 minute.
- Literally with 5 min, I was able to sign up and start using the database.
- Guided tutorial was helpful based on what we want to achieve.
- Setting up a pipeline and starting it from SQL is very nice and handy.
- In a traditional setup, I would have used SSIS, ADF, Informatica or some other ETL to build the pipeline and then load the data.
- It is a time consuming process to build the ETL packages and maintaining the same.
- Literally, with just two sql command I can create and start the pipeline. I like this approach so much.
- It is super fast in processing the very large volume of data. I have loaded 100B records in 40 minutes. The configuration I was using was S-16, 128 vCPU and 1TB RAM.
The CSV file is AWS us-east region and I spun up a maching in Azure Netherlands region. This could be the reason it took 40 min. Otherwise it would have been even faster it was in same availability group.
- In Microsoft SQL Server, I would have used BULK INSERT to load the CSV file. Most of the time, it was painful to do it if the size of the file is huge (more then 2GB).
I will be getting out of memory error due to maching config. Then I go and split the file into several chunk and then try to load. It was never a good experience for me.
But, with singlestore, all I need was two commands to create and start the pipeline. I like this.
I like how SingleStore can be used for different types of data load like streaming and batch data.
- I was trying to see which query is running, but it was asking to start profiling.
- I was not clear whether we have to start profiling to check the active queries and node details.
- Even if we need to start profiling, to check the node details was not making sense to me. We should be able to see the nodes details and what is going on.
- I did not know what to do in Monitoring section. So I started the profiling. The options were not clear for me. I have selected custom timeframe 60 min.
I was under the impression that the profiling will run for 60 min in the background and I can see the active queries and node details.
That could have been better or it could have been communicated to the user better.
- I prefer to access and manage the database from the desktop application. I did not find any desktop application provided by SingleStore.