Database latency – geeky term, but it’s a major problem for state government and federal government program rolls.
A policeman pulls over a speeder. The police computer fortunately picks up that 3 hours ago a similar vehicle and person held up a liquor store – so the police are on alert.
No database latency.
A citizen’s identity is in the DMV registry. They are also on a voter roll and perhaps a retirement program.
If they change their address, they will typically update one of those programs – usually the DMV.
The minute they make that change, they are out of phase with several other government program rolls.
With conventional technology – they are unlikely to have their address changed until many mailers have gone out.
A better method is database synchronization.
Synchronize the major state or federal databases. If a person changes their DMV address, the other systems are flagged – immediately.
Fractal enables that to happen.
Those other programs can contact the person to see if the address change, or other identity change is something that should be reflected in those other programs.
To do this in current technology would cost millions of dollars.
In Fractal, it is native to the Fractal environment – and can be done in a manner where the state does not expend money, it saves money by replacing aging, relational systems at a fraction of their current cost.