4 ms·
Ha, this exact issue bit us in the ass a few months ago. We were working on some streaming Twitter utilities (put in a username and we fire off some events if a
by flyosity 15y ago
Ha, this exact issue bit us in the ass a few months ago. We were working on some streaming Twitter utilities (put in a username and we fire off some events if a mention or a RT of them occurs) and just to test the scalability of our services we entered Justin Bieber. Well one of his tweets got over 100 RTs fairly quickly and we weren't expecting a string to come back. Long story short, it solidly fucked up our event queueing/processing pipeline and brought some of our servers to their knees.
Thanks, Twitter!
- polemic 15y agoReally? An expected response from a foreign (uncontrolled) source brought you servers down? Are you validating responses now, or just assuming they'll never change / always be correct?
- azth 15y agoHooray for type safety?
- sutterbomb 15y agoYup same issue bit me once too - sorting tweets by their RT count doesn't work well when the count is no longer an integer. (Fortunately I was only building a little app for myself to try to learn Ruby and Sinatra.)
- mattdeboard 15y ago"Well, we got a string instead of an integer and yada yada yada, our network almost collapsed." That's a pretty big "yada yada yada" you left out. I am going to assume there's a legit reason why getting a string back instead of another type of reason crippled your servers, but I'd like to know what it was.
- ac2u 15y agoNot alone in testing a heavy stream of tweets using "Bieber" then!