3 ms·

If you don't need transactions, then MySQL with the MyISAM engine has several aspects I love: 1: Blazingly fast. As it simply hands DB writes to the OS and ben

If you don't need transactions, then MySQL with the MyISAM engine has several aspects I love: 1: Blazingly fast. As it simply hands DB writes to the OS and benefits from all the caching and optimization the OS does. Depending on your storage medium, insert/updates/deletes often are 100x faster then with an ACID compliant engine. 2: Simple data structure. Want to see the sizes of your tables? "ls /var/lib/mysql/your_database" and you see each table as two files. One for the data, one for the indexes. 3: Easy to copy the data "cp -r /var/lib/mysql/your_database somewhere" and you are done.

xemdetia 7y ago
As long as your application understands https://dev.mysql.com/doc/refman/8.0/en/internal-locking.html#internal-table-level-locking https://dev.mysql.com/doc/refman/8.0/en/internal-locking.htm... then MyISAM may work for you, it just should be relegated to the second tier option especially for new development. I feel like I have seen so many people overestimate the benefits of MyISAM when they later realize that they can't cleanly write all of the information in a single append unit and have to touch values after the first insert. I generally hope people stop using it as a starting point and instead relegate it to a particular optimization crutch like in-memory tables.