Mysql Cluster vs Percona/Maridb Cluster We want to setup a mysql cluster with master-master sync replication, to provide HA so that one db for write from one app, other for write from other app. It is a webapp with high write and medium read  

We are considering adding mysql cluster and considering percona vs mysql cluster.

Can MySQL ndb cluster import innodb dump ?

Can ndb cluster support MySQL async and 2-way sync replication ?

Can ndb guarantee consistency since it does not write to disk? I.e. What if there is 2 node cluster and both go down and data is not flushed to disk

can ndb cluster support 4-5 table join, ? Will the tables be in same node or will there be any network latency due to distributed joins

Does ndb cluster support MySQL-fabric Python api ?

Does ndb cluster support multi-master bi-directional sync?

Does percona cluster support above items ?
It's hard to say which is "better" -- Percona's PXC or MariaDB w/Galera.  Both use Galera as the underlying "cluster" technology and HA.  Percona is based on Oracle's 5.6, MariaDB is slightly forked back around 5.5 timeframe.  But both are great.

In any case, you really need 3 servers to get HA.  The 3rd is the tie-breaker in case one goes down.

Furthermore, if HA is a big priority, the think about tornadoes, earthquakes, floods, etc.  The 3 machines should not be in the same geographic location.

Bottom line:  Flip a coin for picking between them.  (I'm eager to hear from those who have a strong bias, but if you do, please state whether you have ties to one or the other.)

Don't use NDB Cluster -- it is too far from the main path of things.  There is a lot of setup required, and it has a bunch of limitations.