### 23.2.6 MySQL Server Using InnoDB Compared with NDB Cluster

[23.2.6.1 Differences Between the NDB and InnoDB Storage Engines](mysql-cluster-ndb-innodb-engines.html)
[23.2.6.2 NDB and InnoDB Workloads](mysql-cluster-ndb-innodb-workloads.html)
[23.2.6.3 NDB and InnoDB Feature Usage Summary](mysql-cluster-ndb-innodb-usage.html)

[]()[]()[]()

 MySQL Server offers a number of choices in storage engines. Since both [`NDB`](mysql-cluster.html) and [`InnoDB`](innodb-storage-engine.html) can serve as transactional MySQL storage engines, users of MySQL Server sometimes become interested in NDB Cluster. They see [`NDB`](mysql-cluster.html) as a possible alternative or upgrade to the default [`InnoDB`](innodb-storage-engine.html) storage engine in MySQL 8.0. While [`NDB`](mysql-cluster.html) and [`InnoDB`](innodb-storage-engine.html) share common characteristics, there are differences in architecture and implementation, so that some existing MySQL Server applications and usage scenarios can be a good fit for NDB Cluster, but not all of them.

 In this section, we discuss and compare some characteristics of the [`NDB`](mysql-cluster.html) storage engine used by NDB 8.0 with [`InnoDB`](innodb-storage-engine.html) used in MySQL 8.0. The next few sections provide a technical comparison. In many instances, decisions about when and where to use NDB Cluster must be made on a case-by-case basis, taking all factors into consideration. While it is beyond the scope of this documentation to provide specifics for every conceivable usage scenario, we also attempt to offer some very general guidance on the relative suitability of some common types of applications for [`NDB`](mysql-cluster.html) as opposed to [`InnoDB`](innodb-storage-engine.html) back ends.

[]()[]()[]()

 NDB Cluster 8.0 uses a [**mysqld**](mysqld.html) based on MySQL 8.0, including support for [`InnoDB`](innodb-storage-engine.html) 1.1. While it is possible to use `InnoDB` tables with NDB Cluster, such tables are not clustered. It is also not possible to use programs or libraries from an NDB Cluster 8.0 distribution with MySQL Server 8.0, or the reverse.

 While it is also true that some types of common business applications can be run either on NDB Cluster or on MySQL Server (most likely using the [`InnoDB`](innodb-storage-engine.html) storage engine), there are some important architectural and implementation differences. [Section 23.2.6.1, “Differences Between the NDB and InnoDB Storage Engines”](mysql-cluster-ndb-innodb-engines.html), provides a summary of the these differences. Due to the differences, some usage scenarios are clearly more suitable for one engine or the other; see [Section 23.2.6.2, “NDB and InnoDB Workloads”](mysql-cluster-ndb-innodb-workloads.html). This in turn has an impact on the types of applications that better suited for use with [`NDB`](mysql-cluster.html) or [`InnoDB`](innodb-storage-engine.html). See [Section 23.2.6.3, “NDB and InnoDB Feature Usage Summary”](mysql-cluster-ndb-innodb-usage.html), for a comparison of the relative suitability of each for use in common types of database applications.

 For information about the relative characteristics of the [`NDB`](mysql-cluster.html) and [`MEMORY`](memory-storage-engine.html) storage engines, see [When to Use MEMORY or NDB Cluster](memory-storage-engine.html#memory-storage-engine-compared-cluster).

 See [Chapter 16, *Alternative Storage Engines*](storage-engines.html), for additional information about MySQL storage engines.

