Old meets new

Clustrix secures $10m Series D funding round for NewSQL ascension

Chris Mayer

The NewSQL leaders hope their latest investment will help yield more customers for their scalable, high throughput relational datastore


NewSQL vendor Clustrix has secured a new $10m
funding round to help develop their scale out relational

Founded in 2006, the San Francisco based company
are just one of many “NewSQL” companies to emerge in recent years.
Rather than offering something completely new, like 10gen’s
document store MongoDB or DataStax’s key value store Cassandra,
NewSQL vendors are attempting to meld the worlds of relational and
non-relational databases together by providing the familiarity of a
SQL database with a distributed architecture.

Clustrix provide a “high-scale transaction
throughput” ACID-compliant relational database, with real-time
analytics and parallel processing tacked on. In production since
2008, Clustrix claim to be the leader of the pack, boasting some
impressive large-scale clients like AOL and Symantec. The company
are slightly unusual in their business model, sticking to a
software-only approach

The latest Series D round of investment, led by
HighBar and announced yesterday, takes the market leading Clustrix
$56.5m in total funding, and will
predominantly be used for to “aggressively pursue” the growing
MySQL/ NewSQL market, according to Clustrix CEO Robin

“The need for operational databases that can
analyze data in real-time has never been greater with the rapid
growth of new hyperscale applications in business segments such as
e-commerce, online gaming and advertisement,” he said in a canned

The NewSQL market is undoubtedly growing,
with several companies
jostling to offer an alternative to MySQL and
Oracle. All bring different thinking to the table, yet with so many
vendors chipping away at Oracle’s share, it is difficult to see
which database service will reign supreme at such an early stage.
Ultimately, the biggest challenge for NewSQL vendors remains
convincing companies to part with MySQL, the ones that actually fit
the profile. Some may not even need to.

comments powered by Disqus