Saturday, 25 May 2019

InnoDB vs MyISAM | Storage Engines | Tabular Differences


In this article, we would be discussing Main Differences between Storage Engines like InnoDB and MyISAM, written in Tabular form for great understanding.

InnoDB vs MyISAM | Storage Engines | Tabular Differences
InnoDB vs MyISAM | Full Stack Geek





What Are Storage Engines:

Before moving to the comparison between the two most popular MySQL Storage Engines, we need to know what exactly are these Storage Engines. So, these are basically the underlying software MySQL components. They can handle the SQL operations for different table types (like transactional and non-transactional tables) to store and manage data/information in a database.

InnoDB is mostly used general-purpose storage engine and as of MySQL 5.5 and later it is the default engine. There are many types of Storage Engines, but we would be discussing and comparing only the two most popular ones, InnoDB and MyISAM.

Suggested Read: Redis vs MySQL Benchmarks


Differences between InnoDB and MyISAM:


Basis for Comparision InnoDB MyISAM
Default Presence This is the default storage engine for MySQL 5.5 and higher. This is the default storage engine for MySQL 5.4 and lower.
Locking Row Level Locking Table Level Locking
Referential Integrity and Foreign Key InnoDB is a relational DBMS (RDBMS) and hence has Referential Integrity and supports Foreign Key MyISAM is not an RDBMS and hence does not support Referential Integrity and Foreign Key
Transactions InnoDB supports Transactions (Rollback, Commit) MyISAM does not support Transactions
ACID properties InnoDB supports ACID (Atomicity, Consistency, Isolation, and Durability) properties MyISAM does not support ACID properties
Reliability InnoDB gives reliability as it uses a transactional log to maintain such operations and hence, in case of failure, it can recover easily by using those logs MyISAM offers no data integrity – Hardware failures and canceled operations can cause the data to become corrupt
Performance InnoDB is faster for writes MyISAM is faster for reads
Full Text Searches No Full Text Seacrh in InnoDB Full Text Search is supported in MyISAM

Recommended Articles:

If your learning appetite is still left, you are suggested to read below articles:



Liked this blog? Don't miss out on any future blog posts by Subscribing Here or you can also like our Facebook Page or follow us on Twitter

No comments:

Post a Comment