Share your experience using SingleStore

I have been using SingleStore as a student involved in a project revolving around solutions for business analytics. I am in the process of developing a recommendation system with the help of the product.

SingleStore helps me get the real-time fetch data from a database. I generally use SQL to write a query based on the required solution. In SingleStore, without SQL, if you just give the command, as you do in ChatGPT, then in real-time, it will auto-generate the SQL query and provide me with the solutions based on the RANK function.

Each time, the user cannot write an SQL query for everything owing to certain time constraints. I feel that things can be done quickly in SingleStore since a written command can auto-generate a SQL query in real-time. The speed of the product is good. The support offered by SingleStore is seamless. SingleStore can be used with multiple software tools.

Currently, I can't think of any areas that require improvement because SingleStore was recently launched in the market.

The product can be developed further to provide more appropriate output to users as it is one of the areas where there are shortcomings.

The current SingleStore model provides output based on the RANK function. If a user searches for a liquor bottle, then with all the data the product has, it will search for the liquor bottle in the data, and based on a match, the product has an algorithm to rank the product because of which the paragraph that has the best match will be ranked as a 100, the next one as 99, following which the next product will be ranked as 98 and so on. The output from the solution will fetch you all the 100 products that are available in a store, but sometimes a user might require a product with a 97 or 98 percent match from the DB, meaning the product doesn't always work to provide a 100 percent match, an area I feel that can be optimized in the product.

Currently, SingleStore's features are excellent as it can read documents, images, and everything. The product works seamlessly for me.

I have been using SingleStore for one or two months. I use the solution's latest version.

The solution's stability is fine. Stability-wise, I rate the solution an eight to nine out of ten.

Scalability-wise, I rate the solution a seven to eight out of ten.

Since I haven't reached out to SingleStore's technical support, I am not sure about how to rate their services.

I haven't used any other solution before SingleStore.

The product's initial setup phase was pretty straightforward, with no complex processes.

The solution is deployed on the cloud.

The price of the product is okay compared to the other available solutions in the market. SingleStore is a reasonably priced product, considering the functions it offers.

I did not evaluate any other solutions against SingleStore.

I recommend the solution to those who plan to use it.

I rate the overall tool an eight to nine out of ten.

I use it for managing both transactional and analytical workloads within the same database. In my previous organization, I successfully implemented it for a banking system, where it accommodated transaction-based processes using row store tables and analytical requirements using column store tables. This dual functionality eliminates the need for separate databases for transactions and reporting, streamlining the overall architecture. With SingleStore's distributed architecture, it provides the scalability needed to support diverse workloads effectively.

Its in-memory storage, distributed architecture, scalability, and failover mechanisms collectively contribute to its exceptional performance and reliability, especially in demanding transactional environments like online and mobile banking systems. The ability to store data in memory is a standout feature, enhanced by robust failover mechanisms. Even in scenarios where all servers experience downtime, it ensures data safety by maintaining a copy on disk.

The critical challenge involves optimizing the distribution of data across partitions through careful design of the sharing key. Poor key distribution can significantly impact performance, requiring a backward approach in design rather than adding tables incrementally. Intricate use cases, especially those involving joins across multiple tables, pose challenges if sharing and distribution are not well-aligned. Unlike traditional databases where indexing may suffice, SingleStore may require redistributing the entire dataset, presenting a persistent challenge.

I have been using it for four years.

The stability of SingleStore varies depending on the use case. For a transaction-based system, I would rate it around eight out of ten. However, if it's utilized for an analytical system, I would give it a rating of around seven out of ten.

Scalability is its key strength. Adding servers for scalability is a straightforward process involving simply incorporating a few additional servers and recycling the cluster triggers automatic repartitioning and redistribution of data. For instance, if the initial database creation involved a hundred servers and later, four more servers are added, specific commands can be executed to increase the partitions to one hundred twenty. The data is then efficiently redistributed across the expanded partitions without the need for manual data movement, ensuring a seamless and efficient scalability process. In my current organization, approximately three projects involve the usage of SingleStore, with a team size ranging from ten to twenty individuals.

During the onboarding process at my previous organization, SingleStore provided dedicated support for five to six months, offering invaluable assistance. Presently, with our current service providers partnered with them, support involves raising a ticket, leading to the allocation of a dedicated person for assistance. This personalized approach enables an assessment of the issue, considering factors like data volume. Additionally, the forums serve as a helpful resource for addressing queries, although responses may take a few days. I would rate it eight out of ten.

Positive

We transitioned from using IBM Db2 to SingleStore due to a shift in our infrastructure plan. Initially designed for on-premise deployment, we sought optimized server capabilities for a banking process, with a primary goal of cost reduction compared to mainframe expenses. In our current project, SingleStore is predominantly employed for analysis and reporting purposes. Previously, Palantir and Vertica were used for reporting, but observations of drawbacks in these platforms led to the decision to migrate to SingleStore for more efficient analysis and reporting capabilities, which is proving successful in our current setup.

The initial setup is straightforward, with comprehensive tutorials available on its website. Beginners can easily follow the step-by-step guides, either for a local installation or on cloud platforms like Azure.

The installation process is user-friendly, requiring the selection of a cloud provider and a few configuration choices. Unlike on-premise solutions that involve server setup, SingleStore simplifies the process, making it accessible to a wide range of users. For on-premise installations, specifying server details and failover architecture is necessary, but once the server is prepared, the installation itself is uncomplicated. Database creation involves specifying configurations and requirements, and streamlining the overall setup process.

The platform's versatility allows it to cater to various use cases effectively. Unlike other databases that might require separate solutions for transactional and analytical needs, it offers a unified solution for both. This dual functionality appeals to organizations seeking cost-effective solutions, as they can invest in a single database to address multiple requirements.

Using it for analytical purposes can be cost-effective in the long run, especially in terms of infrastructure. While building an on-premise cluster incurs an initial cost for servers with ample RAM, it becomes a one-time investment with subsequent maintenance handled internally. For cloud deployments, the cost may be relatively higher due to instances offering lower RAM. Opting for higher RAM in cloud instances increases the per-server cost. However, it's important to note that this is a one-time expenditure, and maintenance becomes more straightforward.

I would advise individuals to consider it for transactional systems, particularly if their requirement is for millisecond-level performance. The row store feature is well-suited for such applications. However, it's essential to be mindful of the associated costs, whether deploying on the cloud or on-premise. Due to the need for substantial RAM to store data in memory, the cost can be significant, especially for larger datasets. Overall, I would rate it nine out of ten.