SingleStore aims to deliver the world’s fastest distributed SQL database for data-intensive applications: SingleStoreDB, which combines transactional + analytical workloads in a single platform.
$0.69
per hour
Valentina
Score 7.0 out of 10
N/A
Valentina is a relational database software solution offered by Paradigma Software.
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.
If you have to manage a lot of different databases from different vendors, you could do well by standardizing on this product. It checks all the boxes for a proper database management studio. You would only have to learn one product to manage them all. However, if you are looking to find a good product for a single database vendor, you might be better off finding a tool that was designed specifically for that vendor product.
Foreign Key Constraint data viewer! This was a tremendously helpful feature that not many other products have. Just pick a constraint and see the data in the child tables! No setup required!
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.
Somewhat laggy performance. Boot up speed was on the slow side and connecting to our database servers was also a little slower than other products.
User interface can be a little clunky. Instead of the usual tree view of servers, databases, and schemas, you are presented with lists that you click on and get new windows to pick the new list of data from. Not organized efficiently.
[Until it is] supported on AWS ECS containers, I will reserve a higher rating for SingleStore. Right now it works well on EC2 and serves our current purpose, [but] would look forward to seeing SingleStore respond to our urge of feature in a shorter time period with high quality and security.
SingleStore's performance is incredible. Our predictive algorithms went from taking 24-48 HOURS down to 15 minutes allowing our team to run those much more frequently. Previously, we were limited to about 60 requests per minute due to table locks. Implementing columnstore on SingleStore allowed us to receive 1000 requests per minute.
Very responsive to trouble tickets - Often, I think, the SingleStore's monitoring systems have already alerted the engineers by the time I get around to writing a ticket (about 10 - 20 mins after we see a problem). I feel like things are escalated nicely and SingleStore takes resolving trouble tickets seriously. Also SingleStore follows up after incidents to with a post mortem and actionable takaways to improve the product. Very satisfied here.
We allowed 2-3 months for a thorough evaluation. We saw pretty quickly that we were likely to pick SingleStore, so we ported some of our stored procedures to SingleStore in order to take a deeper look. Two SingleStore people worked closely with us to ensure that we did not have any blocking problems. It all went remarkably smoothly.
Timescale was the biggest alternative option we looked at for SingleStore, however the requirement to learn a new syntax (due to not being SQL compatible) was our biggest pain point. Supporting a new language would require alterations to the Laravel framework, as this only offered SQL integration out of the box. This alteration would be time consuming and would limit our scope to future hiring due to the new syntax.
Compared to Microsoft's SQL Management Studio, Valentina studio was comparable, just harder to get used to in the UI department. It ran slightly slower than other products but did save some time with neat features they baked into the product. However, in using DBeaver Community and DBForge Studio for PostgreSQL from Devart, we found different products that the team ultimately decided to use. DBeaver has all of the features we needed most (minus the constraint data viewer) and a more intuitive UI that we were used to. DBForge Studio for PostgreSQL has a very standard Windows look and feel and lacks some features, like database/table designers, but makes up for those shortcomings in the much easier filtering and sorting options right in the data grids. You can even write a query and edit the data returned, which is something we don't see in many of these tools. Our team ultimately settled on the developers using DBeaver and the support team that needs data viewing/editing capabilities using DBForge Studio.
As the overall performance and functionality were expanded, we are able to deliver our data much faster than before, which increases the demand for data.
Metadata is available in the platform by default, like metadata on the pipelines. Also, the information schema has lots of metadata, making it easy to load our assets to the data catalog.
