MyISAM vs InnoDb - Full-text search versus Fail-safe capability

I in the midst of developing an applications for my wife to ease her daily life as lecturer and suddenly this versus thing trigger me :).


After some digging of information, I switches from InnoDb to MyISAM because I need to Full-text queries highly then insert/update process.

My conclusion:
1. Used MyISAM when your system is highly utilize for viewing and querying.
2. Used InnoDb when your system highly processing insert/update such as logging data or inserting raw data like track-and-trace system.
3. Used MyISAM if your application has the capability to roll-back or hold the data.
4. Used MyISAM if your data will grow beyond 1TB as at this point of time, query will cause problem for InnoDB.

References:

1. http://www.thegeekstuff.com/2014/02/myisam-innodb-memory/
2. http://dev.mysql.com/doc/refman/5.0/en/myisam-storage-engine.html
3. http://dev.mysql.com/doc/refman/5.0/en/innodb-storage-engine.html
4. http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB#comment-115
5. https://www.percona.com/blog/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/
6. http://www.rackspace.com/knowledge_center/article/mysql-engines-myisam-vs-innodb
7. http://dba.stackexchange.com/questions/1/what-are-the-main-differences-between-innodb-and-myisam
8. http://dba.stackexchange.com/questions/1/what-are-the-main-differences-between-innodb-and-myisam
9. https://www.quora.com/How-are-deadlocks-resolved-in-Innodb-vs-MyISAM