3 ms·

This made me giggle

• MichaelGG 12y ago
  Why? A couple years ago I was running a telecom, and we had around that volume of calls a day. Each call required not only routing instructions that hit several DBs, but also a transactional INSERT/UPDATE to account balances. Single node SQL Server handled it fine. (Though it was less than optimal at doing non-OLTP stuff.) Twitter can handle this for people (like DataSift, providing historical lookback), or they can provide template to help them spin up. It's not gonna cost thousands of dollars a month in hardware.