Awesome product
September 11, 2020

Awesome product

Bernard Bardawil | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with MemSQL

SingleStore DB (formerly MemSQL) is currently being used as the MPP DB for our data lake. We use it to ingest different information from the operational platform in order to enable it for app development and analytics. Using SingleStore DB (formerly MemSQL) allowed us to process a high volume of data since it has scalability by design. Memory management in SingleStore DB (formerly MemSQL) is very efficient and even on an infra level the cluster management is straightforward.
  • High data volume processing.
  • Operational data enablement.
  • Redistribution when a node is full.
  • Split processing data usage from data volume license.
  • Faster API integration.
  • Client data integration.
I still use the ones mentioned above in other use cases, and I believe SingleStore DB (formerly MemSQL)'s potential is in what it does best, in our opinion. It's ideal for massive parallel processing. CDH is good for analytics and when you want to build a report over a huge volume. Where SingleStore DB (formerly MemSQL) wins is that it can deliver data on demand, which is the main difference. Between MariaDB and postgres, SingleStore DB (formerly MemSQL) can be presented as an enterprise solution.
The team is always available, responsive, and quite helpful. It is clear by their answers that the support reps are experts in SingleStore DB (formerly MemSQL). They can deliver proper answers and understand the client's environment. I never had an issue that took them long to figure out. They are also ready to walk us through upgrades and have meetings whenever required.
I'm not a data architect so I wouldn't be able to answer this question from that side, but from my perspective, I would say that SingleStore DB (formerly MemSQL) never let us down. We have extremely complex use cases to join different tables with high volumes and the processing power of SingleStore DB (formerly MemSQL) always delivered.

Do you think SingleStore (formerly MemSQL) delivers good value for the price?

Yes

Are you happy with SingleStore (formerly MemSQL)'s feature set?

Yes

Did SingleStore (formerly MemSQL) live up to sales and marketing promises?

Yes

Did implementation of SingleStore (formerly MemSQL) go as expected?

Yes

Would you buy SingleStore (formerly MemSQL) again?

Yes

The way SingleStore DB (formerly MemSQL) is designed is that the different table designs (columnstore, rowstore) give SingleStore DB (formerly MemSQL) the ability to accommodate any scenario, but this also depends on whether someone is willing to invest in SingleStore DB (formerly MemSQL) in simple cases, like master data management storage. SingleStore DB (formerly MemSQL) is good for complex event processing, and it may be seen as an over-engineering choice for simple stuff.