MemSQL Primary Use Case

Data Sleek
Owner at a consultancy with 1-10 employees
When I was working at Wag, MySQL had trouble scaling. We were using an M4-10X RDS instance and three replicas. These machines are expensive and with the growth that the company was experiencing, it was clear we would not be able to scale properly. There were heavy writes done against MySQL that should not have been there; an event table for example. This table was close to 900M rows, taking more than 300GB. I decided to migrate this table to MemSQL, freeing up both lots of space and write resources on MySQL. After the event table was migrated to MemSQL, using the MemSQL built-in S3 pipeline, the table was compressed down to 30GB. View full review »
Find out what your peers are saying about MemSQL, Cockroach, Oracle and others in Relational Databases. Updated: November 2020.
446,956 professionals have used our research since 2012.