Software routinely solves database coordination problems with millions of users per second.
Software routinely solves database coordination problems with millions of users per second.
Even if most of the work is routine, you definitely still want a human in the loop.
A naive view that confuses the map with the territory.
While in a database state you write a row and reality updates atomically....for aircraft they exist in a physical world where your model lives with lag, noise, and lossy sensors, and that world keeps moving whether your software is watching or not. Failed database transactions roll back, a landing clearance issued against stale state does not. The hard problem in ATC is not coordination logic but physical objects with momentum, human agency, and failure modes that do not respect your consistency model.
....if they go around kilometer of the runway the fire will turn into bigger fire
I imagine the training will consist of something like changing the comms protocol to say “runway lights are on, control. Truck 1 confirming cross runway 4D?” prior to crossing. Double check so to speak.
Pilots and controllers speak the same language in the same order; ground vehicles just kinda say stuff.
The aviation-ized version of your proposal would be something like this:
> tower truck 1 short of 4 at delta, red status lights
This isn't a Kubernetes cluster where you can add VMs in 30 seconds.