Fault Tolerance is a feature that allows a system to continue running normally even though there is a broken component in one of its components. Fault tolerant is also used in data transmission so that even if some data fails to receive, the message can be received in full. In storage we recognize RAID where the hard drive is configured so that if there is a damaged hard drive, then the data can be retrieved from the hard drive that is still functioning normally.
We simply understand fault tolerance as tolerance for damage. Here we design so that information systems, especially accounting information systems used by companies can run even though there is damage to the hardware. Here we will discuss how to design a system that continues to run if there is damage at the storage level, at the hardware level and at the level of total damage.
Fault Tolerance deals with high-availability systems.
Failure tolerant handling can be done on:
Data is the heart of the application which has a very important role. Hard drive which is the storage of a computer is an important part of data storage. If the data is corrupted then of course our accounting information system application will experience data chaos. To make fault tolerance on the possibility of a damaged hard disk we can use RAID technology which is short for Redundant Array of Independent Disks.
A software can work well if the memory, processor, netword card and other devices work well. If there is a failure of one of these devices, our application will stop functioning. To create Fault Tolerance on this hardware we can use cloud computing technology.
We might have designed fault tolerant at the storage and hardware levels. But what if there is a major disaster such as a fire? This is where we can do database replication or database clustering where the database is stored in two different geographic locations.