MySQL Server Using InnoDB Compared with NDB Cluster Feature InnoDB  (MySQL 8.0) NDB  8.0 Replication Support Asynchronous and semisynchronous replication using MySQL Replication; MySQL Group Replication Automatic synchronous replication within an NDB Cluster; asynchronous replication between NDB Clusters, using MySQL Replication (Semisynchronous replication is not supported) Scaleout for Read Operations Yes (MySQL Replication) Yes (Automatic partitioning in NDB Cluster; NDB Cluster Replication) Scaleout for Write Operations Requires application-level partitioning (sharding) Yes (Automatic partitioning in NDB Cluster is transparent to applications) High Availability (HA) Built-in, from InnoDB cluster Yes (Designed for 99.999% uptime) Node Failure Recovery and Failover From MySQL Group Replication Automatic (Key element in NDB architecture) Time for Node Failure Recovery 30 seconds or longer Typically < 1 second Real-Time Performance No Yes In-Memory Tables No Yes (Some data can optionally be stored on disk; both in-memory and disk data storage are durable) NoSQL Access to Storage Engine Yes Yes (Multiple APIs, including Memcached, Node.js/JavaScript, Java, JPA, C++, and HTTP/REST) Concurrent and Parallel Writes Yes Up to 48 writers, optimized for concurrent writes Conflict Detection and Resolution (Multiple Sources) Yes (MySQL Group Replication) Yes Hash Indexes No Yes Online Addition of Nodes Read/write replicas using MySQL Group Replication Yes (all node types) Online Upgrades Yes (using replication) Yes Online Schema Modifications Yes, as part of MySQL 8.0 Yes Workload InnoDB NDB Cluster ( NDB ) High-Volume OLTP Applications Yes Yes Table 23.3 Differences between InnoDB and NDB storage engines, common types of data-driven application workloads. 23.1.6.2 NDB and InnoDB Workloads NDB Cluster has a range of unique attributes that make it ideal to serve applications requiring high availability, fast failover, high throughput, and low latency. Due to its distributed architecture and multi-node implementation, NDB Cluster also has specific constraints that may keep some workloads from performing well. A number of major differences in behavior between the  NDB  and  InnoDB  storage engines with regard to some common types of database-driven application workloads are shown in the following table:: 3963