Deleted Comment
I'd take the article with a pinch of salt, they admit they haven't got anywhere near capacity yet, and it doesn't seem like they'd done any real load testing before "final layout". They could easily go the way of most low end VPS providers, day one benchmarks look great and then a few months later when the node fills out and people start using it performances sinks with no lower bound to be seen anywhere.
When the mailperson that delivers your mail currently gets fired by USPS and gets hired by Amazon - do you think much will change in that regard??
Problem #2: It's expensive to support millions of users who post shit
Problem #3: Twitter's revenue base is too small for its cost base
Solution: Eliminate advertising and charge $20 per 1000 tweets. Free to read, costs a tiny bit to tweet.
People who post shit will disappear. People who have an audience and something to say won't bat an eye at this low cost.
If this weeds out 80% of the shit while keeping 80% of the good stuff, Twitter will simultaneously shrink their costs while growing revenues to become a sustainable business.
With this model, Twitter is a $1 billion per year profitable business [2] with a much higher signal-to-noise ratio. [3]
Improve the signal-to-noise ratio and Twitter becomes THE place to be for all kinds of communities. That means a return to growth and higher rates per 1000 tweets.
[1] https://en.wikipedia.org/wiki/Sturgeon%27s_law
[2] Start with 200 billion tweets per year. 90% are shit, and 80% of these go away, leaving 36 billion shitty tweets. 10% are good, and 80% of these stay, leaving 16 billion good tweets. 52 billion tweets in total, monetized at $20 per thousand is a billion bucks a year.
[3] Signal-to-noise ratio before is 1:9, after it's 1:2.
Acer used to do something somewhat similar on some Aspire models (disabling option to enable Vx at BIOS) so using VirtualBox was a no starting, but with some creativity and long winded efi vars mounting and fiddling you could get it working or break your system, not soldering though :)
I'd be interested to see how it pans out Lenovo community admins are worse than Acer community. At least with Dell I find a few engineer on Twitter and ping them..
When I started with CouchDB it wrong choice for so many reasons, client had <30gb of data, couchdb was cooler than node.js, and I was frustrated with SQL Server. In hindsight sticking with SQL Server or Postgresql would of been better - older/wiser today.
And that's what Google, Facebook, and Amazon, at the very least, have done: bought fiber, hired network engineers, and designed things that work efficiently for them. If YouTube is 90% of Google's traffic, it's not surprising that Google's network looks like a CDN. Amazon wants to interconnect their AWS datacenters to lower their internal traffic costs. Facebook wrote a new routing protocol (Open/R).