In today's RDBMS scenario, MyISAM engine is being replaced by Innodb engine due to its lower concurrency, less support for database transactions and referential integrity constraints. There are many more reasons of migration from MyISAM engine to Innodb engine, these are discussed as follows:

• As the database size grows, Innodb offers better reliability in comparison to MyISAM. Innodb recovers from a crash in fixed amount of time by replaying its logs. While recovery in ISAM depends on the size of the data files. The more are the database files, the more time it will take.
• InnoDB engine is faster than MyISAM engine as it performs the read/write operations within the engine itself by combining the row caches with the index caches. MyISAM, on the other hand, relies on the operating system for caching read and write operations.
• Innodb provides ACID (Atomicity, Consistency, Isolation, Durability) compliant transaction support, which is not available in MyISAM.
• Innodb storage engine reduces the loss of transactional integrity to the maximum extent.
• Innodb offers greater reliability and availability of MySQL database in comparison to MyISAM.