SingleStore is very well at the current stage, but I see room for improvement in ease of administration, monitoring, and reducing troubleshooting time. Better documentation for advanced use cases, especially where data volumes are very high and queries are frequent, would help us manage the feature more efficiently. Expanding integrations and providing more built-in tools would also improve the overall experience. For our use case, I would appreciate out-of-the-box integrations with commonly used data ecosystem tools and built-in monitoring and observability capabilities for SingleStore. The dashboards could be more intuitive for performance tracking, query optimization insights, and overall administrative management. This would make our day-to-day operations easier, allowing us to gain more insights and use SingleStore better with improved visibility on ongoing processes.
I have noticed that SingleStore can be improved because the integration of SingleStore with DataDog is not good. The data which is sent to DataDog sometimes does not match with the SingleStore dashboard.
SingleStore can be improved in the aspect that the Azure pipelines do not have many parameterization features compared to others, for example, AWS. Also, error handling needs attention. When it fails due to memory, it only indicates that but not exactly in which process it failed. I would like to add that we need to know what the roadmap of SingleStore is. An additional improvement needed is that the semantic layer can be better. Currently, it requires significant development experience to fine-tune queries.
Senior Data Analyst at a comms service provider with 1,001-5,000 employees
Real User
Dec 6, 2023
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.
Data Analytics Solution Architect at Cinergie Digital
Real User
Mar 15, 2023
The documentation has room for improvement. There is not a large active community. I would like to have step-by-step documentation to assist even a novice with installation. Having the ability to migrate servers using a single command would be extremely beneficial. At present, there are numerous steps required to configure and migrate pipelines.
There should be more pipelines available because I think that if MemSQL can connect to other services, that would be great. MySQL to MemSQL replication would be great. If it could replicate from MySQL then this would allow me to move all of the heavy counts, full-text search, aggregate, and analytical queries off of MySQL. We would not need many replicas, and you could have near-real-time (less than a few seconds) data you that can report on, and generate these reports in less than a few seconds.
SingleStore delivers the performance you need for enterprise AI, providing the most performant data platform for apps and analytics at scale. SingleStore enables organizations to scale from one to one million customers in one unified platform. SingleStore offers transparent pricing as shown here https://www.singlestore.com/pricing/
SingleStore caters to over 400 customers globally, including major banks and tech companies in 50+ countries and 40+ verticals. It offers seamless scaling for...
SingleStore is very well at the current stage, but I see room for improvement in ease of administration, monitoring, and reducing troubleshooting time. Better documentation for advanced use cases, especially where data volumes are very high and queries are frequent, would help us manage the feature more efficiently. Expanding integrations and providing more built-in tools would also improve the overall experience. For our use case, I would appreciate out-of-the-box integrations with commonly used data ecosystem tools and built-in monitoring and observability capabilities for SingleStore. The dashboards could be more intuitive for performance tracking, query optimization insights, and overall administrative management. This would make our day-to-day operations easier, allowing us to gain more insights and use SingleStore better with improved visibility on ongoing processes.
I have noticed that SingleStore can be improved because the integration of SingleStore with DataDog is not good. The data which is sent to DataDog sometimes does not match with the SingleStore dashboard.
SingleStore can be improved in the aspect that the Azure pipelines do not have many parameterization features compared to others, for example, AWS. Also, error handling needs attention. When it fails due to memory, it only indicates that but not exactly in which process it failed. I would like to add that we need to know what the roadmap of SingleStore is. An additional improvement needed is that the semantic layer can be better. Currently, it requires significant development experience to fine-tune queries.
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.
We don't get good discounts in Pakistan.
The documentation has room for improvement. There is not a large active community. I would like to have step-by-step documentation to assist even a novice with installation. Having the ability to migrate servers using a single command would be extremely beneficial. At present, there are numerous steps required to configure and migrate pipelines.
There should be more pipelines available because I think that if MemSQL can connect to other services, that would be great. MySQL to MemSQL replication would be great. If it could replicate from MySQL then this would allow me to move all of the heavy counts, full-text search, aggregate, and analytical queries off of MySQL. We would not need many replicas, and you could have near-real-time (less than a few seconds) data you that can report on, and generate these reports in less than a few seconds.