What does Clustrix offer that MariaDB Cluster within its MariaDB TX offering not?
MariaDB acquires Clustrix
11–20 of 31 posts
Re: MariaDB acquires Clustrix
#12First they picked up infinidb a while back and have been working to mainline "mariadb columnstore". Now the acquisition of Clustrix and discussion of mainlining that also. It looks like MySQLs separation of the storage engines is paying off in their ability to keep one interface but allowing significantly different backends to meet the different workload requirements. There has been a lot of work expanding the storag…
How is this any different from what MemSQL is already doing?
Re: MariaDB acquires Clustrix
#13Early Clustrix employee here. Holy cow that took a long time! 12 years since the company was founded and finally they exit. I can't wait to exchange my illiquid startup stock for... stock in a _different_ private company.
So it was a 100% stock purchase? Bummer man.
Beats the stock turning into toilet paper.
Re: MariaDB acquires Clustrix
#14Early Clustrix employee here. Holy cow that took a long time! 12 years since the company was founded and finally they exit. I can't wait to exchange my illiquid startup stock for... stock in a _different_ private company.
So it was a 100% stock purchase? Bummer man.
I don't actually know the terms yet, I just assumed. I only learned of the acquisition from hackernews.
Re: MariaDB acquires Clustrix
#15Re: MariaDB acquires Clustrix
#16I was unfamiliar with Clustrix. It looks like they've been around a while (YC06) and have some sophisticated technology ( http://docs.clustrix.com/display/CLXDOC/Distributed+Database... ). A horizontally scalable drop in replacement for MySQL is nothing to sneeze at. https://www.clustrix.com/
I think it's in-memory. There is mysql-ndb-cluster free.
I spent a lot of time at a previous job supporting an NDB cluster and I can attest first hand that it is awful.
Single node failures cause entire cluster shutdowns, the cluster then takes forever to recover and must be done in a specific order. In fact just thinking about it makes me anxious.
Re: MariaDB acquires Clustrix
#17First they picked up infinidb a while back and have been working to mainline "mariadb columnstore". Now the acquisition of Clustrix and discussion of mainlining that also. It looks like MySQLs separation of the storage engines is paying off in their ability to keep one interface but allowing significantly different backends to meet the different workload requirements. There has been a lot of work expanding the storag…
I had high hopes for MyRocks, then I got a chance to use it. The limitations, mainly being 5.6 and no coexistence with InnoDB made me reevaluate TokuDB and it was a better choice for a write heavy, low update, workload especially with interval flushing (non-fsync durable) commits.
Re: MariaDB acquires Clustrix
#18First they picked up infinidb a while back and have been working to mainline "mariadb columnstore". Now the acquisition of Clustrix and discussion of mainlining that also. It looks like MySQLs separation of the storage engines is paying off in their ability to keep one interface but allowing significantly different backends to meet the different workload requirements. There has been a lot of work expanding the storag…
I had high hopes for MyRocks, then I got a chance to use it. The limitations, mainly being 5.6 and no coexistence with InnoDB made me reevaluate TokuDB and it was a better choice for a write heavy, low update, workload especially with interval flushing (non-fsync durable) commits.
I am using as well MariaDB + TokuDB with "a write heavy, low update, workload especially with interval flushing (non-fsync durable) commits" => do you have maybe a short list of the limitations of MyRocks in MariaDB for this area?
I tried to use MyRocks (never used it before) in MariaDB some months ago but couldn't find almost any docs and ultimately didn't understand which parameters were supposed to be set how under which condition... .
Re: MariaDB acquires Clustrix
#19Earlier quoted context omitted.
I think it's in-memory. There is mysql-ndb-cluster free.
I spent a lot of time at a previous job supporting an NDB cluster and I can attest first hand that it is awful. Single node failures cause entire cluster shutdowns, the cluster then takes forever to recover and must be done in a specific order. In fact just thinking about it makes me anxious.
What version was this ?
Re: MariaDB acquires Clustrix
#20I was unfamiliar with Clustrix. It looks like they've been around a while (YC06) and have some sophisticated technology ( http://docs.clustrix.com/display/CLXDOC/Distributed+Database... ). A horizontally scalable drop in replacement for MySQL is nothing to sneeze at. https://www.clustrix.com/
We used it at a previous employer of mine. It had a few quirks but in the end, it saved the company from a mountain of technical debt by allowing us to avoid a huge rewrite to address database scaling issues that were becoming intractable.