I have built an application as part of my UG thesis that uses mysql database (community edition). Now, my professor wants me to provide fault-tolerance to the database (by parity!!)! I argued that we wouldn't need that. Anyway I searched, and found here that mysql has built-in replication engine (a mechanism to provide fault-tolerance, right?), along with many other techniques to provide reliability. But what I learned from there is that there is a master server and some slave servers to provide the fault tolerance using replication. Now my questions are:
What if I have only one database server? Does mysql have any fault-tolerance for single standalone database servers (i.e. no master-slave formation, no cluster, etc.)?
Do I need to try to provide any kind of fault-tolerance whatsoever for the data stored in mysql database?
What kind of differences are there (in terms of fault-tolerance only) between community edition and enterprise edition of mysql servers?
Somehow I get the feeling that we don't need to do anything for providing fault-tolerance to mysql db, and it is fine by itself. But I need some solid info on the matter.
The second question from above again:
Do I need to try and provide any kind of fault-tolerance whatsoever for the data stored in mysql database?
What is the sensibleness of trying to provide fault tolerance to a mysql database by using parity (bit per byte)?
A little details about the data in the database:
The data to be specific is a collection of about 6500 Unicode strings, less than 1 MB in size, is initialization data, that will never change over time. The only transaction will be to read the data from the database, no update no delete. My application requires full-text search on those strings, and this is the only reason I am using mysql since it provides full-text search. I am aware that I could avoid mysql's FT search by using something like elasticsearch instead.