> So in this example, it might be that you distribute your requests to servers based on how over or under loaded the servers are.
They had a working approach to distributing requests to servers, described at the beginning of the article. It's sessions (aka connections or channels in Google's literature) they're focusing on.
Responding also to siscia's grandchild comment:
> Or you can spin up more machines. The integral and derivative part will tell you when spinning up more machines or when to tear down the one you already got!
You're describing something like Google's autopilot, which I just linked to in another comment. A PID controller might make sense there, but it's only tangentially related to the problem described in this article.