Consuming rate-limited APIs at scale is like interacting with a database that has pretty painful latency. I keep "inventing" what are surely preexisting design patterns / solutions to this problem. Can anyone point me to a good guide so that I can stop wasting my time?
Yea, that's my fear and why I've designed with a very polite client. But I guess threat of ban is worth the complexity cost.
-
This Tweet is unavailable.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.