This might be somewhat unrelated; Is there any reason Stack Overflow decided against deploying on something like the Open Compute Project.
Very likely because at just 6 racks of commodity (i.e. orderable without a salescritter) hardware, they don't need that density or scale.
Stack Overflow: The Hardware – 2016 Edition
21–27 of 27 posts
"Don't fix what ain't broken"
Re: Stack Overflow: The Hardware – 2016 Edition
#22Interestingly, the price of 32GB DDR3 LR-DIMMs has been falling as well. I wonder if this is due to oversupply or something else since 8Gbit DDR3 will never happen on servers.
Re: Stack Overflow: The Hardware – 2016 Edition
#23Do you have any plans to run on .NET Core? If so, how soon after it's out as RTM? Any issues with this?
These plans are in flux. At a core level (heh), we nee to have libraries ported first anyway. So we're doing that now. Jil, StackExchange.Redis, Dapper, and Sigil are up on NuGet and core compatible today (some as pre-release). Others like Exceptional are just pending some RC2 goodness to release, and I'll be starting on MiniProfiler after that. We'll likely post other internal tools to .Net Core and start heavy testing in the RC2 time-frame.
Will we run Stack Overflow on core? Probably not for a while. I was asked exactly this in a recent On.Net interview at the 24:22 mark; you can listen here for reasoning: https://youtu.be/DJn8-Psznsw?t=24m22s
Re: Stack Overflow: The Hardware – 2016 Edition
#24Earlier quoted context omitted.
Very likely because at just 6 racks of commodity (i.e. orderable without a salescritter) hardware, they don't need that density or scale.
"Don't fix what ain't broken"
This, more than anything.
There's no compelling reason to invest in such a move for our situation. We're very interested in how Open Compute progresses, though.
Re: Stack Overflow: The Hardware – 2016 Edition
#25Re: Stack Overflow: The Hardware – 2016 Edition
#26Re: Stack Overflow: The Hardware – 2016 Edition
#27Now I've seen the Matrix from outside