That is, in fact, exactly what we typically see in reality with local access control system head-ends.

At the doors, there might be keycards, biometrics and PINs (oh my!) happening.

But there's usually just not much going on, centrally. It doesn't take much to keep track of an index of IDs and the classes of things those IDs are allowed to access.

I have a little fanless mini PC that runs various stuff around my house, including homeassistant. The case is basically a big heat sink.

It started crashing during backups.

The solution was to stick a fan on it. :( This is literally a box _designed to not need a fan_. And yet. It now has a fan and has been stable for months. And it's not even in a closet - it's wall-mounted with lots of available air around it.

You must be young. We used to have handhelds and computers with no cooling at all.

>You can't just shove it in a closet with zero thought and expect it to not overheat/shut down/catch fire

Actually in almost all products meant for real companies doing real work, this is an explicit design requirement.

Every cash register runs off of a computer that sits in a tiny metal oven with no cooling and is expected to run 24/7 without fail.

The difference between a tech gadget and a real world, real purpose appliance.

There are card access systems that don’t require a computer, just a microcontroller. Perhaps if you need to integrate with multiple sites or a backend system for access control rules you can add computers, but card access systems are dead ass simple for a reason; they need to be reliable. The good systems that have computers still allow access in the event of a network failure.

Any access control system that fails in the event that it loses internet connectivity is poorly designed.

You're saying that as if we never had Z80-based microcontrollers doing all this without problems. Complete with centralized control and all.