What is SingleStoreDB not for?
SingleStoreDB excels at real-time and high throughput query use cases. It is a general purpose database for running both transactional and analytic workloads. However, there are use cases which SingleStoreDB is not designed to run. Some of these are listed below:
Object store. SingleStoreDB is not designed to be a blob store. It is designed for high value data that is structured or semi-structured and ready to query. SingleStoreDB has open-source connectors for integrating with a variety of object stores, including Amazon S3 and Hadoop File System (HDFS).
See Load Data for more information.
Running on low hardware. SingleStoreDB 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 SingleStoreDB for development is to use the Cluster-in-a-Box Docker deployment option; see Single-host.
In-process database. SingleStoreDB is not run as a library or in-process with an application. SingleStoreDB is a distributed database which runs in separate processes from the application, and applications connect to SingleStoreDB via a client driver.