Hello,

I'm starting the development of a new project

The DB will be used to store hundreds of thousands of products ( probably millions), thousands of such products will be updated every day.
This database will be used to power several websites, I don't expect the traffic to explode on these sites, but I don't want to build something with no chances to perform well.

MyISAM or INNODB? I continue to find opinions of any kind on this subject

how would you prevent websites to be slow while the database is being updated ( hence being hit by thousands of SELECT/INSERT/UPDATE queries) ?

MyISAM for read-only tables and for fulltext search

InnoDB for foreign key data integrity and row-level locking on updates

InnoDB

So you suggest using two separate tables, one Innodb for backend INSERT/UPDATE operations and one, MyISAM, for websites.

What would be the best approach to create the MyISAM table from the InnoDB table content?

Simply using something like this?
are there smarter/faster methods?

What about a view?

that's not exactly what i meant

i would use innodb exclusively unless i had a reason to need myisam, and then i would not duplicate the data either