4 ms·
You could maintain a local cache which is updated less frequently and a blacklist which gets pushed everywhere when updated. Why is it a requirement to be able
by TheAceOfHearts 5y ago
You could maintain a local cache which is updated less frequently and a blacklist which gets pushed everywhere when updated.
Why is it a requirement to be able to instantly revoke a person's badge access eeverywhere in real time anyway?
- zamadatix 5y ago> You could maintain a local cache which is updated less frequently and a blacklist which gets pushed everywhere when updated. 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.
- account42 5y agoA couple of seconds delay for the blacklist to propagate is not going to make a difference for a stolen card.