memsql

If MySQL was a drop-in replacement for MemSQL, you wouldn't need MemSQL in the first place.

If you're asking whether this client will work with memsql, then the answer is No.

MemSQL (YC11) - San Francisco, CA - Onsite MemSQL is working to build the next great database company.

VoltDB for transactions and ingestion-time analytics and MemSQL for deeper analytics might be a neat combo system.

MemSQL has an incredibly high-caliber team at one of the most exciting high-growth companies in tech.

MemSQL partitions data across nodes by hash, not by range, so partition prunning is less applicable.

As another example, MemSQL don't shard, and use a lock-free index (they use concurrent skip-lists).

At least in that case the 'community' could move to MariaDB, which is not an option for non-Free databases like MemSQL.

MemSQL is a Y-Combinator company delivering the leading real-time database for transactions and analytics.

The database engine team is responsible for building the core database engine behind MemSQL.

The reason you chose MemSQL is probably because it offers something that MySQL doesn't.

We are looking to literally move all of our internal stuff to memSQL community edition while keeping our customer tools on enterprise.

"but will run on commodity hardware" We run memSQL 4.0 on 18 machine cluster, all commodity hardware.

All I can say is "it's on the roadmap.":) I used to do a lot of analytics at Facebook and am now a PM at MemSQL, so it's one of my priorities.