I remember taking a PL class in undergrad, learning Prolog as one of a handful of languages. During that section my brain started to want to "bind" variables to things as I was going about my day, it was very weird.
To mitigate this case you could limit capacity in terms of concurrency instead of request rate. Basically it would be like a fairly-acquired semaphore.
I felt this keenly when my children were very young. At times I only had one arm/hand free because I was holding a child in the other. Or I could only read poorly in the dark because I didn’t want to turn on the lights and disturb the kids.
Since then I always see accessibility thinking as a universal benefit, not just for the “abled”.
When I was in college they would use a transparency projector, but instead of transparency pages, there would be a roll with a crank that you would turn to advanced the roll. You would get the same effect as slipshow.
I am responsible for a MapReduce-based system built about 13 years ago and it is the bane of my team’s existence right now. It was the hotness in its day, but did not age well at all. We are working on a replacement using ClickHouse.