MemSQL is Great for Use Cases where Performance (Latency and Data Freshness) Needs are High
Rating: 9 out of 10
September 01, 2021
Vetted Review
Verified User
2 years of experience
We use MemSQL for a particular slice of our OLAP use cases: client-facing UI dashboards that have solid query latency and data freshness requirements (generally 4 9s under 2 seconds, although we try to get under 1, and data replication and recalculation in under a second), and on small to medium size data sets (10s of GB for fact data, GBs or 10s of GBs of dimension data). It is currently owned by a data platform team that supports client-facing use cases from a number of product teams.
- Data replication.
- Joins.
- Small data set processing in memory.
Cons
- User defined functions.
- Providing optimization options.