SingleStore DB

What is SingleStore not for?

SingleStore excels at real-time and high throughput query use cases. It is a great general purpose database for running both transactional and analytic workloads. However, there are use cases which SingleStore is not designed to run. Some of these are listed below:

  • Object store. SingleStore is not designed to be a blob store or data lake. It is designed for high value data that is structured or semi-structured and ready to query. SingleStore has open-source connectors for integrating with a variety of great object stores, including Amazon S3 and Hadoop File System (HDFS).

    See Load Data for more information.

  • Running on low hardware. SingleStore is not designed to run on micro instances, mobile phones or other low-powered computers. It is designed to run on machines with at least 4 cores and 8GB of RAM. The easiest way to run SingleStore for development is to use the SingleStore Cluster-in-a-Box Docker deployment option; see Single-host.

  • In-process database. SingleStore is not run as a library or in-process with an application. SingleStore is a distributed database which runs in separate processes from the application, and applications connect to SingleStore via a client driver.

  • Serializable transactions. SingleStore supports extremely fast, distributed READ-COMMITTED transactions, as well as SERIALIZABLE transactions through the use of SELECT … FOR UPDATE.