As in, "the duration of a ping to the US and back" slow.
Yep, every badge in and out in the whole office had to go cross-continental (before the door unlocked).
As in, "the duration of a ping to the US and back" slow.
Yep, every badge in and out in the whole office had to go cross-continental (before the door unlocked).
while (!bright) { increaseBrightnessBy10%(); sleep(100ms); }
and
while (!dark) { decreaseBrightnessBy10%(); sleep(100ms); }
Then someone had to log into a server and reboot a process before the blinking stopped.
Of course it isn't a no-brainer:
- It is still a non-trivial amount of data for an embedded device.
- You want to be able to revoke quickly.
- You still want to log the access if offline (and how big should that buffer be?).
You could set the system up to push data out to all of the badge readers whenever there is a change, but that's a big messy operation. A more complex but probably workable solution is to have them readers cache the data but also have the server maintain a list of those caches, and when someone is changed you invalidate all of the readers that the person used within the last cache timeout period. Even then it is still messy, if a reader has temporarily lost network connectivity their cache could be out of sync. It's one of those problems that gets really hairy once you're down in the weeds working out the details.
Luckily this isn't a pure IT system, but bound to physical bodies moving around. Some delay is acceptable. Most likely the person is already in anyways.
Why is it a requirement to be able to instantly revoke a person's badge access eeverywhere in real time anyway?
That seems like the system GP just described, including the hairiness you can get into.
> Why is it a requirement to be able to instantly revoke a person's badge access everywhere in real time anyway?
With 140,000 employees and hundreds of locations across the globe it becomes a question of dealing with hundreds of local databases and dealing with people that need to be in more than 1 or 1 central database (be it truly centralized or cache coherent).
Also think beyond the "you're fired and standing right in front of me" use case of revocation for why it's a requirement it be instant. A lost/stolen/replicated card can have traveled the world in the time it takes to be realized compromised.
Any office that uses physical keys will fail to meet this requirement, and we've had that system for quite a long time and it seems to have worked alright.
And I can't imagine why would anyone think otherwise.
Of course, if the employee was indeed a ninja, your guards wouldn't be able to do much, but in all other cases, it will suffice.
We all derided the company that made "smart" pet feeders that wouldn't maintain a cache of the feeding schedule, but rather phone home to check; when their servers were down, pets went without food. It's not difficult to think of an scenario like this.
You could maintain strong consistency while having fast local reads, once you have entered a building in a country it pulls you into the local range. So you're only slow when switching.
Did Nest smoke detectors have to go to the cloud?