TrustRadius: an HG Insights company

SingleStore

Score7.5 out of 10

110 Reviews and Ratings

What is SingleStore?

SingleStore aims to enable organizations to scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.

Read more details.

Videos

SingleStore is Fast and Furious

Use Cases and Deployment Scope

I use SingleStore for the data warehouse of a fintech, which processes payments through TCs worldwide. The integration was with Azure DataFactory, without complications, it helps us in an excellent way since we are very fast in obtaining the data for our dashboards and additionally the compression of the information.

Utilizo SingleStore para el datawarehouse de una fintech, la cual procesa pagos mediante TCs a nivel mundial, la integracion fue con Azure DataFactory, sin complicaciones, nos ayuda de manera excelente dado que tenemos mucha rapidez en obtener los datos para nuestros dashboards y adicional la compresion de la informacion

Pros

  • Fast Data Recovery
  • Data compression by 80%
  • Having the information in sheets, which helps to process the information quickly
  • Simplicity in TSQL
  • Recuperacion de Datos de manera rapida
  • Compresion de datos en un 80%
  • Tener la informacion en hojas, lo que ayuda a procesar la info rapidamente
  • Simplicidad en TSQL

Cons

  • Azure pipelines do not have many parameterization features compared to others, for example AWS.
  • Error handling, for example when it fails due to memory, only indicates that but not exactly in which process it fell.
  • a more detailed profiler
  • Direct purchase through partners, but buying directly from the brand, I think, would be better without intermediaries.
  • los pipelines para Azure no tienen muchas caracteristicas de parametrizacion en comparacion con otros, ejemplo AWS
  • El manejo de errores, por ejemplo cuando falla por memoria solo indica eso pero no exactamente en que proceso cayo
  • un profiler mas detallado
  • la compra directa a travez de partners, sino comprar directo a la marca creo que seria de mejor manera sin intermediarios

Return on Investment

  • Our internal clients are happy to have the data quickly.
  • Making decisions based on data with a 2-hour delay to the transactional database is excellent since we go from 24 hours to 2 hours.
  • I think the best comparison is decision-making with data that is close to reality.
  • nuestros clientes internos estan felices al tener la data de manera rapida
  • el tomar decisiones en base a datos con un lapso de delay de 2 horas hacia la base de datos transaccional es excelente ya que bajamos de 24 horas a 2 horas
  • la mejor comparativa creo que es la toma de decisiones con datos apegados a la realidad.

Alternatives Considered

Exasol

Other Software Used

Azure Data Factory, Microsoft Power BI, Metabase

DBA using SingleStore point of view

Use Cases and Deployment Scope

We use the SingleStore as our OTLP side to our Vertica as DWH.
the purpose is to do things fast like PII or Enrich data .
we load the most of the data straight from Kafka and it's working pretty well.

Pros

  • pipelines - load data from variety of sources
  • availability of the cluster and redundancy
  • high performance - queries run fast on SingleStore
  • shard tables

Cons

  • we need to know what is the road map of SingleStore
  • I think some feature are still not mature enough
  • AMD cpu not supported as Intel cpu
  • I think SingleStorehas a long way

Return on Investment

  • pretty easy to implement a solution
  • need to design the tables in order to work fast
  • the ROI is good

Alternatives Considered

MariaDB Platform and MySQL

Other Software Used

Apache Kafka, OpenText Vertica, Apache Airflow

Why I like SingleStore ?

Use Cases and Deployment Scope

We use SingleStore for a super fast client experience, running real time analytics on billions of events arriving every day from various publishers channels.

Pros

  • Performance - Milliseconds response of 80 tables Joined queries
  • Scalability - Ability to grow with no downtimes
  • Client success - Attentive to business needs, deep level support, patches and fixes
  • Efficiency - Built-in Kafka / S3 / MySQL integrations well adjusted to leverage SingleStore architecture and hardware
  • .
  • .
  • .
  • .
  • .

Cons

  • Add Iceberg tables / files Pipeline
  • CDC out in form of logfile / binlog / producer to Kafka
  • Efficiency with multi shard-key use case: Joined three tables when one of them holds both shard keys of the other two.
  • .
  • .
  • .

Return on Investment

  • Graded as the top leaders in the field
  • Client satisfaction
  • Innovate with each new major release

Other Software Used

Confluent, Snowflake

The future is HTAP

Use Cases and Deployment Scope

We use SingleStore as the primary database for our Digital Marketing OS. It allows us to process transactions and answer complex analytical queries within the same database.

Pros

  • HTAP workloads
  • query profiling and explanations
  • customer support

Cons

  • visibility over memory management
  • the code source is closed, so we can't audit it for backdoors
  • would help to manage cluster settings via the UI without SQL

Return on Investment

  • SingleStore simplified our tech stack
  • It improved the capabilities of our software with real-time analytics

Alternatives Considered

MongoDB and PostgreSQL

Other Software Used

MySQL

Great database solution for apps that require analytics and those who don't want to juggle db providers

Use Cases and Deployment Scope

We are using SingleStore to power our whole app database layer.
We use it both for our basic tables and also for the analytical ones.

The magic is that we don't need to have multiple types of databases, it's just a single database which is a drop-in replacement for MySQL and it works almost exactly the same at the API level with some differences, which we can live with but hope they can improve upon (like column adjustments on the fly, foreign keys, etc.)

Pros

  • Analytical queries
  • Basic SQL usage similar to how you would use MySQL

Cons

  • Column mutations (from null to not null, or type changes)
  • Foreign keys
  • Unique columns (for columnstore)

Return on Investment

  • No engineering overhead for maintaining the db so no makes up for the price in a way
  • We are able to provide better analytics to our customers - providing more value

Alternatives Considered

ClickHouse and Elasticsearch

Other Software Used

Hetzner IaaS, Symfony, Vue.js