In February 1967, Erna Schneider Hoover filed a patent application from Bell Laboratories. She had drafted parts of it on a yellow legal pad while recovering in a maternity ward after the birth of her second daughter. Four and a half years later, on November 23, 1971, the U.S. Patent Office issued US Patent 3,623,007 — "Feedback Control Monitor for Stored Program Data Processing System." It is one of the earliest software patents ever granted.

To grasp why it mattered, picture the crisis it solved. Electronic switching systems (Bell's brand-new 1ESS) processed phone calls by scanning incoming lines, queuing tasks, and dispatching them to a central processor. When call volume spiked — Mother's Day, a snowstorm, a Super Bowl — the queue would overflow. The switch would seize up, drop calls, or worse, drop the line status of connected calls, leaving people talking into dead handsets. Existing overload controls were crude and reactive: cut off input entirely, dump the queue, reboot.

Hoover, a mathematician with a Yale PhD in philosophy of symbolic logic, saw the switch not as a phone system but as a control problem. Her patent proposed monitoring the rate at which the processor was actually completing tasks, comparing it continuously to the arrival rate, and using that ratio as feedback to throttle low-priority work before the queue exploded. If the system was falling behind, non-urgent scanning tasks were deferred; high-priority call setups still got through. The system self-regulated instead of collapsing.

Read that again. Monitor demand. Compare to capacity. Shed lower-priority load to keep the critical path healthy. That is, quite precisely, what every modern:

• TCP congestion control algorithm does with packet flows (Van Jacobson's 1988 work is a direct descendant of this thinking)
• Cloud auto-scaler does — AWS Auto Scaling, Kubernetes' Horizontal Pod Autoscaler, GCP's managed instance groups
• API rate limiter does — token buckets, leaky buckets, adaptive concurrency limits at Netflix, Uber, Stripe
• Circuit breaker does — Netflix's Hystrix, Envoy's outlier detection, Istio's traffic policies
• CDN load balancer does when it routes around a hot origin

Hoover's insight — that a system under load should measure itself and gracefully degrade rather than crash — is the closed-loop feedback philosophy that keeps every hyperscale service alive. In 2024, when Cloudflare's traffic engineers describe "backpressure" or Google's SRE book talks about "adaptive throttling," they are describing the same control-theoretic idea Hoover formalized for a telephone switch.

What makes the patent genuinely surprising is who and when. In 1967, "software" was barely a category the patent office knew what to do with. Hoover's filing had to be argued as a novel apparatus — the software controlling a physical switching system — because pure algorithms were considered unpatentable. She was also, at that moment, one of the very few women technical supervisors at Bell Labs; she was promoted while on maternity leave, partly on the strength of this work.

The 1ESS switch and its successors ran on Hoover's control loop for decades, quietly handling billions of calls. When those switches were finally retired in the 2000s and traffic migrated to IP networks, the feedback principle didn't retire — it migrated with it, into every reverse proxy, every message broker, every serverless dispatcher on Earth.

She was inducted into the National Inventors Hall of Fame in 2008. Most engineers who write rate.NewLimiter() today have never heard her name.