1/ I think I may have been overthinking things. Now I'm using an API bridge server that *almost* just passes requests to the twitter API, but also does rate limit management, retries, and connection pooling.https://twitter.com/generativist/status/1158424894067003392 …
2/ Since it's streaming responses back to the reader, I'm not too concerned about resource allocation problems during cursored collection. I'm also not doing async requests anymore (I don't think). So aborted requests are cancel cursoring.
-
-
3/ The only concerns are long-running cursors and their associated problems. But, I think this is a whole lot less complex and I like it (so far).
Show this thread -
4/ Next up: figuring out a good way to use (and gcloud deploy)
@dgraphlabs...Show this thread
End of conversation
New conversation -
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.