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.
Do you think SingleStore delivers good value for the price?
Yes
Are you happy with SingleStore's feature set?
Yes
Did SingleStore live up to sales and marketing promises?
Yes
Did implementation of SingleStore go as expected?
Yes
Would you buy SingleStore again?
Yes