Talk:Software fault tolerance
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
 | The contents of the Fault-tolerant software page were merged into Software fault tolerance on 28 February 2019. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
Copyright problem removed
editPrior content in this article duplicated one or more previously published sources. Copied or closely paraphrased material has been rewritten or removed and must not be restored, unless it is duly released under a compatible license. (For more information, please see "using copyrighted works from others" if you are not the copyright holder of this material, or "donating copyrighted materials" if you are.) For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or published material; such additions will be deleted. Contributors may use copyrighted publications as a source of information, but not as a source of sentences or phrases. Accordingly, the material may be rewritten, but only if it does not infringe on the copyright of the original or plagiarize from that source. Please see our guideline on non-free text for how to properly implement limited quotations of copyrighted text. Wikipedia takes copyright violations very seriously, and persistent violators will be blocked from editing. While we appreciate contributions, we must require all contributors to understand and comply with these policies. Thank you. Moonriddengirl (talk) 03:26, 1 January 2013 (UTC)
Blog-like writing style, full of opinions and very detached from reality.
editFollowing design patterns should be combined together to make the system more fault tolerant: retry, fallback, timeout, circuit breaker, and bulkhead pattern.
This isn't Wikipedian language at all and is terribly vague. Something along the lines of "Fault tolerant software often practice these design patterns: ..." would be much better.
To make your system more fault tolerant, you should measure 99th percentile latency and keep the remaining 1% (aka tail latencies) in check through self healing mechanisms.
That is a very, extremely, subjective definition of "fault tolerant software", seemingly pulled out of nowhere?
The only thing constant is change. This is certainly more true of software systems than almost any phenomenon
Not at all how wikipedia is supposed to read AFAIK, this is very blog-like. And having a citation on this specific line is hilarious.
The need to control software fault is one of the most rising challenges facing software industries today. Fault tolerance must be a key consideration in the early stage of software development.
says who?
"Computer applications make a call using the application programming interface (API) to access shared resources, like the keyboard, mouse, screen, disk drive, network, and printer. These can fail in two ways.
- Blocked Calls
- Faults"
make a call to who? using the API of what? to access shared resources of what?
Who says they can fail in only these two very specific weird way? Who wrote this??
The entire article is just a bunch of gobbledygook glued together Usernames.are.hard.ngl (talk) 10:53, 6 February 2025 (UTC)