i may be using the wrong example here However, i think this may be the reasons for overnight payment updates.
In certain countrie this may happen differently but in gerneral i believe this is common usage. Assume there is a telephone bill payment system. On due date the customer were adivced to make payment from any Telecom Branch. So beleive the Telcom may have
a version of a Centralized database each branch having a slave database and when the customer pays his bill at branch "A" he was told that the payment will be credited to the account overnight. So this is a batch updating system. This may be seems dumb but
assume the customer wants to test the system. and he goes to another branch, brnach "B" and attempts to pay the same bill. Assuming that there arent any text printed on the bill quoting that it was already paid. The Teller and Branch "B" access his account
by typing the account code or what ever. Remember that he was told at branch "A" that his account will be updated overnight. So the updated slave database in branch "A" will batch update overnght till them the master DB has the old account details indicating
that he hasn't paid the bill. Since branch DBs are not linked, brnach B cannot access db of branch A. therefore the system will accept payment from him for the same bill ag
View Complete Post