4 ms·
Excuse me for, maybe, stupid question, but: we have few (250+) InnoDB tables and triggers - if we will try to move all data to Clustrix, will our application co
by EugeneOZ 14y ago
Excuse me for, maybe, stupid question, but:
we have few (250+) InnoDB tables and triggers - if we will try to move all data to Clustrix, will our application continue to work? I've read about "drop-in replacement" but maybe somebody here already have experience in same issue.
- sergei 14y agoIt's a good question. We built the entire database from the ground up, without any MySQL code. So while we support most of the frequently used features, we don't support everything. You can get a list of unsupported features and differences from our docs: http://docs.clustrix.com/display/CLXDOC/Unsupported+Features http://docs.clustrix.com/display/CLXDOC/Unsupported+Features http://docs.clustrix.com/display/CLXDOC/Feature+Differences http://docs.clustrix.com/display/CLXDOC/Feature+Differences Having said that, our customers find that the value that they get out of scale out, fault tolerance, and performance is worth the tradeoffs of not supporting every single MySQL feature. Honestly, our goal is not to be 100% MySQL compatible. We're aiming to be compatible enough to capture a significant share of existing MySQL installs, but we're really after building a truly scalable relational db.
- EugeneOZ 14y agoThanks. In your blog I've found: "The database has native support for dealing with JSON documents." Why it's not in the features list? I thinks it's very cool.