MyISAM vs Innodb vs Memory, Which Storage Engine for MySQL?

If your website uses MySQL database, then you have the option between Storage Engine is InnoDB, MyISAM and MEMORY to suit your needs. When you choose the correct Storage Engine, Mysql will have the best performance, optimized MySQL will have better results, when your websites can receive the most traffic without downtime for your Mysql before you decide to upgrade VPS/Server. What about you? which one would you choose for your site? MyISAM or Innodb or Memory?

The features that come with Innodb makes it much easier to choose Innodb for me.
while it has a lower storage limit than MyISAM, it is more stable and crash safe.
MVCC, Foreign Key Support, crash safe, Data cache and ACID Properties is only a few of the advantages that it has over MyISAM and Memory.
Memory is the last option that any one should go for and when choosing between Innodb and MyISAM you should consider what you will be using it for. as MyISAM is more suitable for higher storage needs (cheaper and higher limit)

MyISAM and MySQL
MyISAM Storage Engine is the type most commonly used. This Storage Engine allows indexing the whole column (Full text index) so that it read access speed for the fastest performance.
However it is very poor in the "insert / update" data. So if your website is mainly cms as wordpress blog, you should choose this type of Storage Engine.

InnoDB in MySQL
InnoDB Storage Engine is newer MyISAM, this Storage Engine is the best for Forums have constantly updated amount.
Speed ​​insert/update/delete operations preferably by Row Level Locking mechanism so when updating (Add, delete, edit) 1 table, only the records are being locked alone operations, other operations on this table still occur normally. But its drawback is cost more RAM to operate than MyISAM.

MySQL MEMORY
Engine MEMORY (HEAP) engine speed is retrieved and updated best because it stores data directly to RAM. Therefore it is used as the data table contains three or user session. When restart MySQL or Server, all data will be erased.

I'm using InnoDB in most of my websites, but I always use a caching solution to limit as much as possible the queries amount.
There is nothing faster than the NoSQL solutions like Redis or MongoDB. In a Web Server, the first components which use too much resources is always MySQL.