Data Synchronisation
The work of keeping the same numbers on every device, so a phone in a van, a second branch and the office all agree.
Also known as data sync keeping data in step two-way sync
Definition
Data synchronisation is the plain business of making sure two devices show the same numbers. The tablet in the delivery van, the till in the second shop and the computer in the office all hold a copy of the same information. Synchronisation is the work that keeps those copies in step.
Most owners meet the idea on the day the numbers stop agreeing. The main branch says twelve boxes are left. The second branch sold four of them an hour ago and nobody in the office knows. A system that synchronises properly sends every sale to one central record within seconds, then pushes the new count back to every screen. That is how Storek, the shop system from Linkysoft, keeps one stock number for the whole business instead of one per branch.
Then there is the van. A driver takes an order in a village with no signal. Good software lets him carry on and saves the order on the phone itself. When the phone finds a connection, it sends everything it collected, in the order it happened, and pulls down whatever changed while he was away. That is called working offline. It is far more common in real jobs than software companies like to admit.
The hard part is a conflict. Two people edit the same customer record at the same minute, from different places. One changes the phone number, the other changes the address, and the software has to decide which version survives. Some systems keep the newest change and quietly drop the other. Some keep both and ask a person to choose. Neither is wrong. You just need to know which one you bought.
So ask three questions before you sign anything. How long is the gap between a sale in one branch and the number changing in another. What happens to a full day of work done on a phone that had no internet. And when two people edit the same record, whose version wins, and does anyone get told. Linkysoft puts these on the first call of any web application project, because the answers change both the price and the build. One honest note: perfect synchronisation does not exist. There is always a small delay, and a supplier who admits it is safer than one who promises none.
Questions about Data Synchronisation
How long should synchronisation take between two branches?
What happens to orders taken on a phone with no internet?
What is a conflict, in plain words?
Do I need synchronisation if I only have one shop?
Still not sure how this applies to your project?
Tell us what you are building and we will answer in plain language.