A classic (pedagogical) example is that of the faulty bank account software application. Imagine that Kaloor (needless to say, fictional names and figures have been employed here), a freelance sculptor, has an account with his bank; his current balance is $12,000.00. Two transactions, deposits of $3,000 and $8,000, which are payments for work he has successfully completed, are issued simultaneously. It does not take a genius to see that (assuming that there are no other transactions), very soon, his account balance should reflect an amount of $23,000.00.
For the purpose of this example, let's visualize that the banking software application is a multithreaded process; to keep things very simple, we consider ...
